|
| From: | Paul Brook |
| Subject: | Re: [Qemu-devel] [PATCH] fix gdbstub support for multiple threads in usermode, v2 |
| Date: | Tue, 2 Jun 2009 22:14:22 +0100 |
| User-agent: | KMail/1.11.2 (Linux/2.6.29-2-amd64; KDE/4.2.2; x86_64; ; ) |
> > > thread #3 will have the same cpu_index as thread #1, which would > > > confuse GDB. > > > > Really? Why doesn't GDB get confused on real machines when the PID wraps? > > Is the real bug that we're missing some sort of thread > > creation/destruction event reporting? > > Hm, this is a good point. I think the bug is that: >... > I'm also not sure what to do differently that doesn't involve making > QEMU remember what happened to all the threads it's seen until GDB asks > about them. Ideas? Ok, from Daniel's response it sounds like this bit of gdb is broken. Could we use the real TID? Seems silly to invent a new value when the host has already found one for us... Paul
| [Prev in Thread] | Current Thread | [Next in Thread] |