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] |
Not all architectures that run linux need PC adjustment. You're thinking x86-linux. Anyway, I meant that you're breaking setting a user breakpoint on top of a permanent breakpoint. Try setting a breakpoint with "break *int3_addr", on top of that int3, and running to it. When it is hit, you're moving the PC passed it, so later calls to bpstat_stop_status like:
/* See if there is a breakpoint at the current PC. */ ecs->event_thread->stop_bpstat = bpstat_stop_status (stop_pc, ecs->ptid);
... will not see the permanent breakpoint, right?
Mark's point about considering a trap instruction as a normal instruction is valid, so I'm not sure if we'd want to do this skipping by default or not. I'll let you guys fight over it. :-)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |