Re: Help. Program coredumps with SIGILL after exit (0) is called
From: Aurelian Melinte (amelinte_at_b504.info.polymtl.ca)
Date: 05/31/04
- Previous message: Lew Pitcher: "Re: Calling a Windows DLL"
- In reply to: Anis: "Help. Program coredumps with SIGILL after exit (0) is called"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 31 May 2004 14:20:49 GMT
Anis <anismo@yahoo.com> wrote:
> Any help with regard to what I should be looking at the find a
> resolution
Hi,
One thing you could do is to install a SIGILL handler and from within use backtrace() and backtrace_symbols() - those are specific to gcc. This probably would not tell you much more than the core though.
another technoque I found very useful is to link with ElectricFence - you will
find memory problems right away and not much later at exit time or when
returning from some obscure function with a corrupted stack
HTH
a.
>
>
- Previous message: Lew Pitcher: "Re: Calling a Windows DLL"
- In reply to: Anis: "Help. Program coredumps with SIGILL after exit (0) is called"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
