Re: Program receiving SIGSEGV after exit()
- From: Alejandro Pulver <alepulver@xxxxxxxxxxx>
- Date: Sat, 30 Dec 2006 11:13:52 -0300
On Sat, 30 Dec 2006 14:15:57 +0200
Kostik Belousov <kostikbel@xxxxxxxxx> wrote:
On Sat, Dec 30, 2006 at 03:10:35AM -0300, Alejandro Pulver wrote:
Hello.Use _exit() instead of exit() in the handler. Aside question is whether
The port "games/qudos" keeps running in a loop after exiting from the
main menu. This is because after calling exit() the program receives a
SIGSEGV signal, and the signal handler, after intercepting it, calls
exit() again.
I think it is a problem with the application itself, but I don't know
what to look for in the source code.
I have attached a 'gdb' backtrace.
Could someone please point me in the right direction?
Thanks and Best Regards,
Ale
this handler is needed at all.
Hello.
Thank you for your reply.
I searched in the SVN repository and found it originally was _exit(),
but changed to exit() just before the release, and after that it was
backed out.
Yes, I guess the handler is not very useful (also it doesn't produce a
core file like the default one).
Best Regards,
Ale
Attachment:
signature.asc
Description: PGP signature
- References:
- Program receiving SIGSEGV after exit()
- From: Alejandro Pulver
- Re: Program receiving SIGSEGV after exit()
- From: Kostik Belousov
- Program receiving SIGSEGV after exit()
- Prev by Date: Re: Program receiving SIGSEGV after exit()
- Next by Date: Re: Program not being executed at all
- Previous by thread: Re: Program receiving SIGSEGV after exit()
- Next by thread: Program not being executed at all
- Index(es):
Relevant Pages
|
|