[Kde-pim] Re: I need help by testing kmail2 with gdb and --nofork

Thomas McGuire mcguire at kde.org
Sun Jan 16 19:18:57 GMT 2011


Hi,

On Sunday 16 January 2011 18:32:36 Guy Maurel wrote:
> As notice at the beginning of kmail-main I try:
> $ cgdb kmail
> (gdb) set args --nofork
> (gdb) show args
> Argument list to give program being debugged when it is started is
> "--nofork". (gdb) run
> Starting program: /usr/local/bin/kmail --nofork
> [Thread debugging using libthread_db enabled]
> 
> ...
> kmail: Unknown option 'fork'.
> kmail: Use --help to get a list of available command line options.
> 
> Program exited with code 0376.
> 
> What do I do wrong?

You're not doing anything wrong, this is caused by a bug in kdelibs.
Happens sometimes as well for me, and sometimes not, I don't know the reason.
If you don't need to debug KMail startup, you can attach the debugger to an 
already running kmail with "cgdb --pid `pidof kmail`"

Regards,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20110116/fb87e42a/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list