Remote, embedded debugging
Niko Sams
niko.sams at gmail.com
Fri Jun 3 23:10:21 BST 2011
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?
And the second thing... well, does that fix anything? It just breaks
in main - you could also
add that breakpoint using the breakpoints toolview.
Niko
On Fri, Jun 3, 2011 at 16:47, Leon Pollak <leonp at plris.com> wrote:
> Just to add my 2c about the remote debugging I do with Kdev for the last 5
> years...
>
> The last trunk version still has the same problems with breakpoints and
> starting the gdb.
>
> I do two following workarounds:
>
> 1. Recompile the kdevelop with file kdevelop/debuggers/gdb/debugsession.cpp
> line 1082 comment out 'else'.
>
> 2. Put 'br main' into your .gdbinit file.
>
> These two things will allow break points and remote loading to work.
>
> Hope this helps.
>
> --
>
> Leon
>
> _______________________________________________
> kdevelop mailing list
> kdevelop at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop
>
>
More information about the KDevelop
mailing list