This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Daniel, Thanks for your help. Here attached is a log between Eclipse and GDB. GDB stops on a breakpoint where it is supposed to display a value and then continue. Unfortunately, it seems that it first informs Eclipse that it stops and Eclipse query infos about threads, stack-frame... and the commands attached to the breakpoint are never executed. When GDB stops on a breakpoint with commands associated, does it inform the front-end with MI commands ? if yes, is it after executing the commands or before ? Thanks, David On 1/23/06, Daniel Jacobowitz <drow@false.org> wrote: > On Mon, Jan 23, 2006 at 11:41:32AM +0100, David Lamy-Charrier wrote: > > Hello, > > > > I am using minGW GDB 6.3.1 on a windows XP Pro PC, and I am using > > breakpoint commends to do some tasks each time a breakpoint is reached > > and then continue execution. > > Everything is working really fine with GDB only and with Insight. > > (this is definitely a powerfull feature, I can also use hook-stop to > > do the same ). > > > > But when I try it with Eclipse front-end connected to gdb through MI > > commands, it stops working: > > GDB stops on my breakpoint but it does not execute the commends > > associated to the breakpoint and it does not continue execution. > > > > I turned on MI logs to see what happens and it appears that GDB sends > > a "*stopped\n" message to Eclipse, Eclipse sends commands to get infos > > on threads, stack frame... and GDB never executes my commands and > > never continue execution. > > > > Has anybody already encountered this problem ? > > Do you think it will be easy for me to modify GDB to workaround this > > problem? any hints on the files I should looked at ? > > There is not enough information here to understand your problem. > Can you send a full log of the communication between GDB and Eclipse > that shows what's going wrong? > > -- > Daniel Jacobowitz > CodeSourcery >
Attachment:
eclipse_gdb_log.txt
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |