This is the mail archive of the gdb-patches@sources.redhat.com 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] |
What to do about the threaded case? GDB is having so much trouble getting it right that I'd like to make sure gdbserver does from the start.
I guess this can be handled completely in the linux-low wrapper functions by switching the current thread and setting watchpoints for each. I think that is correct for all Linux targets using hardware watchpoints, because of the nature of Linux threading.
For CRISv32, there might be an additional problem lurking in the shadows: we treat the watchpoint registers as global (i.e., only one process at a time can use them, and thus they are not saved/restored on context switches etc).
Anyway, is this something you want resolved before I commit the CRIS/CRISv32 support? (Here's an updated ChangeLog entry and updated patches if not.)
-- Orjan Friberg Axis Communications
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |