Re: Os X Frontend development: Why sending SIGTERM?

On Mon, 2004-06-28 at 16:23, Manuel Holtgrewe wrote:
> However, Using the latest source release (0.8.9) the program "crashes" 
> with SIGABRT on the start process... As far as I could track the error, 
> the function "init_configfile" (defined in settings.c) always sends a 
> SIGTERM "signal()" in line 705:

No, signal() adds a signal handler. It doesn't send any signal. SIGABRT
happens because abort() is called. Usually because some assert() failed.
You should see where it really crashes by getting backtrace with gdb.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBA9SPqyUhSUUBViskRAie2AKCQSb1M25XayyAF5B+TRiZ7baaRYQCgnZuh
+HR8MXjV8/0l1OZQBnMn2Fo=
=MCUt
-----END PGP SIGNATURE-----