Re: I need help by testing kmail2 with gdb and --nofork

2011-01-18 Thread Valentin Rusu
> On Monday 17 January 2011 20:04:49 Thiago Macieira wrote: >> On Monday, 17 de January de 2011 18:28:52 Guy Maurel wrote: >>> What is happening? Is it really a problem at kdelibs? >> Yes. Please debug KCmdLineArgs and KUniqueApplication. > Has anybody a method to look at that? > Well, on my setup

Re: I need help by testing kmail2 with gdb and --nofork

2011-01-18 Thread Guy Maurel
On Monday 17 January 2011 20:04:49 Thiago Macieira wrote: > On Monday, 17 de January de 2011 18:28:52 Guy Maurel wrote: > > What is happening? Is it really a problem at kdelibs? > > Yes. Please debug KCmdLineArgs and KUniqueApplication. Has anybody a method to look at that? Thanks -- guy >> V

Re: I need help by testing kmail2 with gdb and --nofork

2011-01-17 Thread Thiago Macieira
On Monday, 17 de January de 2011 18:28:52 Guy Maurel wrote: > What is happening? Is it really a problem at kdelibs? Yes. Please debug KCmdLineArgs and KUniqueApplication. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Framewo

I need help by testing kmail2 with gdb and --nofork

2011-01-17 Thread Guy Maurel
Hello! I'm using the trunk. 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 libthrea