This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: mi/674: GDB/MI No way to know the current selected thread
- From: Salvador Eduardo Tropea <salvador at inti dot gov dot ar>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 25 Aug 2004 20:38:00 -0000
- Subject: Re: mi/674: GDB/MI No way to know the current selected thread
- Reply-to: Salvador Eduardo Tropea <salvador at inti dot gov dot ar>
The following reply was made to PR mi/674; it has been noted by GNATS.
From: Salvador Eduardo Tropea <salvador@inti.gov.ar>
To: gdb-gnats@sources.redhat.com, alain@qnx.com,
gdb-prs@sources.redhat.com
Cc:
Subject: Re: mi/674: GDB/MI No way to know the current selected thread
Date: Wed, 25 Aug 2004 17:35:48 -0300
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view audit-trail
In my frontend I use the thread indicated by the last async "*stopped"
that I got.
I always keep the last "stopped" response.
SET