This is the mail archive of the gdb@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] |
> ????? Memory is shared between threads, isn't it so ????
This is yet another long overdue problem (I had hope it was fixed in recent releases) - gdb lumps together mult-process debugging with multi-tread debugging and it it does not excell in any of them.
You mean GNU/Linux?
I guess you didn't mean GNU/Linux.It seems to me that we have to handle multi-process debugging a-la vxWorks with a separate gdb instance per process and thus forget about it.
When reading or writing memory, gdb specifies a thread. If it turns outthat the thread disappeared, GDB picks a thread, any thread (the assumption being that all address spaces are pretty much similar). Mind you, I've seen thread implementations that implemented per-thread local data using VM.It does not mean that everybody else should suffer, it is time to fix this youthful indiscretion.
Humor me. So who is suffering? Andrew
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |