[Debian GNUstep maintainers] Bug#568049: gnumail.app: GNUMail systematically segfaults at startup

[Ian D. Leroux]

On Wed, 03 Feb 2010 11:24:33 +0000
Yavor Doganov <yavor at gnu.org> wrote:
> Just to be sure, could you run a crashing app in gdb, and when it
> stops on SIGABRT, check how many gdnc instances are running?

At the moment of the crash I have as many instances of the daemon as I
had before starting the app:
- If I have a gdnc already running, then when GNUMail receives SIGSEGV
  while running in gdb there is still one instance of gdnc running.
- If I killall gdnc and then start GNUMail in gdb, there are no gdnc
  instances running when GNUMail receives SIGSEGV.
So it seems that the app isn't starting gdnc on its own. 

I've tried sending a SIGINT (^C) while the app was starting up (still
under gdb) instead of waiting for the SIGSEGV, with the same results.

> Let's try something very simple first.  Install libgnustep-base-dev
> and compile the attached program with "gs_make".  Then
> run ./obj/nctest.

$ obj/nctest 
2010-02-03 08:56:10.328 nctest[30840] <GSNotification: 0x10c1d10> Name:
Notification Object: <NSObject: 0x1070580> Info: (nil)
2010-02-03 08:56:10.332 nctest[30840] <GSNotification: 0x10c1d10> Name:
Notification Object: (nil) Info: (nil)
Posting a simple notification appears to work.
Total notifications: 2

$ ./obj/test '{a=b; c=d}' '(foo, bar)' --batch '(setq foo 1)'
Useless info about bundle: <NSBundle: 0x11da940>
</home/idleroux/GNUstep-tests/Resources/test>
'{a=b; c=d}' - a dictionary.
'(foo, bar)' - an array.
'--batch' - a string.
'(setq foo 1)' failed with:
Parse failed  - Parse failed at line 1 (char 7) - unexpected character
(wanted ',' or ')').
Failure.

Exit status was 1 after the latter test.