Remote, embedded debugging
Niko Sams
niko.sams at gmail.com
Sat Jun 4 17:35:15 BST 2011
On Sat, Jun 4, 2011 at 00:57, Leon Pollak <leonp at plris.com> wrote:
> On Saturday June 4 2011, Niko Sams wrote:
>
>> Hi,
>
>>
>
>> The first workaround is needed because you use a gdb script (configured in
>
>> the launch configuration). If you use a gdb script kdevelop doesn't "file"
>
>> or "run" for you,
>
>> as you are supposed to do that in your script.
>
>> Is that a wrong assumption?
>
> Without this, kdevelop does not react to run/cont command always being in
> 'run' state.
Ok, so do you "run" in your script?
>> And the second thing... well, does that fix anything? It just breaks
>
>> in main - you could also
>
>> add that breakpoint using the breakpoints toolview.
>
> If I do not put 'br main' in the start script, the breakpoints in the BP
> view are not set and application does not stop at all.
Ok, I see.
Now I need a way to reproduce this on my machine. Could you help me with that?
Niko
More information about the KDevelop
mailing list