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

List:       kde-panel-devel
Subject:    Re: [Panel-devel] KUniqueApplication Debugging
From:       Vinay Khaitan <vkhaitan () gmail ! com>
Date:       2005-08-30 17:17:20
Message-ID: 56c534770508301017109f23e0 () mail ! gmail ! com
[Download RAW message or body]

pasting the output...

kde4@ishwar:~> kicker --nofork
DCOPRef::send(): no DCOP client or client not attached error
kicker: Unknown option '--nofork'.
kicker: Use --help to get a list of available command line options.


On 8/30/05, A. Wiedenbruch <mail@wiedenbruch.de> wrote:
> Am Dienstag 30 August 2005 18:33 schrieb Vinay Khaitan:
> > Debuggers are very useful to understand code-flow and complete design.
> > I have earlier used Debugger to understand even complex XMLGUI
> > framework successfully.
> >
> > But Kicker is a kuniqueapplication. and kuniqueapplication has a
> > unique thing, it forks child process.
> > While stepping through function, I found that, there it starts whole
> > kicker. We can't step through because of fork.
> > Perhaps, stepping ASM instructions may let even forked process debug.
> > Is there any way known ??
> 
> Have you tried starting kicker with the --nofork parameter?
> _______________________________________________
> Panel-devel mailing list
> Panel-devel@kde.org
> https://mail.kde.org/mailman/listinfo/panel-devel
>
_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel

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