RE: [cdt-dev] Behaviour of thread-select mi command

["Mikhail Khodjaiants" <Mikhail.Khodjaiants@xxxxxxx>]

Hi,

Thread selection in the debug view is not synchronized with GDB. We had
it in the early versions and it was the source of many problems.
Currently the context (selection) is passed to GDB and it internally
switches to the required thread and stack frame.
Try GDB console, I don't see any other workaround for this case. 

Regards,
Mikhail

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Mike Wrighton
Sent: Wednesday, November 19, 2008 3:56 PM
To: CDT General developers list.
Subject: [cdt-dev] Behaviour of thread-select mi command

Hi,

I've got a question about thread selection in the debug view and how
this relates to the gdb mi commands. Basically when execution is
suspended, I would expect clicking on a thread in the debug view to
result in a thread-select for that thread. What I'm seeing however is
several thread-selects, the last one being a thread-select x where x was
the original thread (always thread 1 in my case). Unfortunately in my
system, breakpoints are always thread-specific, and to set a breakpoint
you must be on the current thread (e.g. if you want to set a breakpoint
on thread 2 then you click thread 2 before you set the
breakpoint) so this doesn't work.

Can anyone shed any light?

Cheers,
Mike
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

-- 
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.