[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-debug-dev] Re: Using CDT as avr-gdb frontent for AVR tar get platforms
|
Note that GDB init scripts are not a cureall.
There be dragons!
E.g. my manual attach to target sequence is:
(gdb) target remote 192.111.111.111.2000
(gdb) monitor reset
(gdb) set $pc=0x1030000
(gdb) c
"monitor reset" is asynchronous!
There is no way for GDB to know when "monitor reset" has completed!
Also, sometimes launching fails after "(gdb) c", which I can determine by manually
examining the result of that command.
>The problem is that right now there is no simple mechanism which
>allows the caller of the gdb process creation to intervene once
>the gdb has been started, but before it has done anything meaningful.
Also, I want CDT to throw out the concept that there is only one debug session
per GDB session.
In a single GDB session I can start a new debug session anytime, e.g.
by rerunning the command sequence above.
--
Øyvind Harboe
http://www.zylin.com
