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

[Pawel Piech <pawel.piech@xxxxxxxxxxxxx>]

Bring up breakpoint properties and look at the "Filter" page.
-Pawel

P.S. Surprisingly it's not in the user documentation: http://help.eclipse.org/ganymede/topic/org.eclipse.cdt.doc.user/tasks/cdt_o_brkpnts_watch.htm

Mike Wrighton wrote:

Hi Pawel,

I'm not sure exactly what you mean, where is the thread filter?

Mike

2008/11/19 Pawel Piech <pawel.piech@xxxxxxxxxxxxx>:
  

Hi Mike,
Did you try setting the thread filter?  This will result in the -p option
being used with break-insert, which may have the same effect.

Cheers,
Pawel

Mike Wrighton wrote:
    

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

      

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

    

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