This is the mail archive of the gdb-patches@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]

Re: [rfc] linux-nat: Never PTRACE_CONT a stepping thread


On Sun, 17 Oct 2010 21:04:18 +0200, Pedro Alves wrote:
> I just belatedly realized that this probably
> breaks software single-step archs though.  :-/

I have run the testsuite on arm-fedora12-linux-gnu and the only
regression-candidate there is gdb.threads/local-watch-wrong-thread.exp .

But that one is reproducible even on x86_64-fedora14snapshot-linux-gnu just by
`set can-use-hw-watchpoints 0'.  That testcase in fact should not have
executed on arm due to:
	if [target_info exists gdb,no_hardware_watchpoints] { return 0; }

Checking more why that change happened.

I do not see why it should fail in general.  insert_single_step_breakpoint
already supports two existing single step breakpoints, one gets used for
inferior_ptid and one for stepping ptid.  Maybe the support of two single step
breakpoints is there for some inferior code constructs, in such case
I understand two would be no longer enough.


Thanks,
Jan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]