This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Thread switching and stepping bug
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: Thread switching and stepping bug
- From: David Smith <dsmith at redhat dot com>
- Date: Fri, 04 May 2001 10:27:51 -0500
- CC: Jonathan Larmour <jlarmour at redhat dot com>, gdb at sources dot redhat dot com
- Organization: Red Hat, Inc.
- References: <3AE541F1.C8D1976F@redhat.com> <3AE57FA9.5090009@redhat.com> <3AEF64C7.790438AB@redhat.com> <3AF00AA7.6020002@redhat.com> <3AF1F8AB.5040504@cygnus.com>
Andrew,
I'm a bit nervous about making it the default. Although I believe that it
would certainly help 99% of targets, I worry about the last 1%.
Would there be some way of just turning this on for targets that support threads?
Andrew Cagney wrote:
>> Jonathan,
>>
>> Note that my patch provides the generic PREPARE_TO_PROCEED
>> functionality. You'll have to change your tdep file to use
>> generic_prepare_to_proceed(). If your target is already multi-arched,
>> it is a one line change in your {target}_gdbarch_init() function. It
>> would look like this:
>>
>> set_gdbarch_prepare_to_proceed (gdbarch, generic_prepare_to_proceed);
>>
>> Give that a shot.
>
>
> Perhaphs the generic version should be enabled by default?
>
> While this is definitly a departure from the norm - retain default
> behavour even when broken - I suspect it may still be better since
> enabling this fixes a bug.
>
> Andrew
--
David Smith
dsmith@redhat.com
Red Hat, Inc.
http://www.redhat.com
256.704.9222 (direct)
256.837.3839 (fax)