[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: where's --nofork gone?
From:       Melchior FRANZ <mfranz () kde ! org>
Date:       2004-05-05 16:27:31
Message-ID: 200405051827.31415 () pflug2 ! gphy ! univie ! ac ! at
[Download RAW message or body]

* Waldo Bastian -- Wednesday 05 May 2004 18:21:
> konsole doesn't have --nofork because it doesn't fork.(konsole itself that is,
> it does start a shell-process of course)

Oh, then I have to look again. I set a breakpoint in Konsole::Konsole that was
never reached, because konsole was reportedly forked and the watched process had
ended. Hmm ...

  $ gdb `which konsole`
  GNU gdb 5.3.92
  [...]
  (gdb) break main
  Breakpoint 1 at 0x80486c2: file konsole.la.cpp, line 2.
  (gdb) r
  Starting program: /usr/local/kde/bin/konsole
  [New Thread 16384 (LWP 30064)]
  [Switching to Thread 16384 (LWP 30064)]
  
  Breakpoint 1, 0x080486c2 in main (argc=1, argv=0x1) at konsole.la.cpp:2
  2       int main(int argc, char* argv[]) { return kdemain(argc,argv); }
  (gdb) break konsole.cpp:333
  Breakpoint 2 at 0x4005a31f: file konsole.cpp, line 333.
  (gdb) cont
  Continuing.
  kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-m/ksycoca
  Detaching after fork from child process 30074.


I should probably take some gdb lessons ...

m.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]