public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: David Smith <dsmith@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jonathan Larmour <jlarmour@redhat.com>, gdb@sources.redhat.com
Subject: Re: Thread switching and stepping bug
Date: Fri, 04 May 2001 08:28:00 -0000	[thread overview]
Message-ID: <3AF2CA77.9070907@redhat.com> (raw)
In-Reply-To: <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)

  reply	other threads:[~2001-05-04  8:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24  2:06 Jonathan Larmour
2001-04-24  6:33 ` David Smith
2001-04-24  8:14   ` Jonathan Larmour
2001-05-01 18:37   ` Jonathan Larmour
2001-05-02  6:30     ` David Smith
2001-05-03 17:32       ` Andrew Cagney
2001-05-04  8:28         ` David Smith [this message]
2001-05-10  8:33           ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AF2CA77.9070907@redhat.com \
    --to=dsmith@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).