Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] stept, nextt, finisht, untilt, continuet
Date: Tue, 30 Aug 2011 09:16:00 -0000	[thread overview]
Message-ID: <20110830091623.GA5329@host1.jankratochvil.net> (raw)
In-Reply-To: <20110830014851.78030246131@ruffy.mtv.corp.google.com>

On Tue, 30 Aug 2011 03:48:51 +0200, Doug Evans wrote:
> Sometimes I want to run with scheduler-locking on, but having to turn it on,
> perform the command, and remember to turn it off afterwards is annoying.

Please no, Fedora already has default `set scheduler-locking step' because
this is what the users expect from the stepping commands.

What are the reasons for not using `set scheduler-locking step'?

IIRC there was some (ppc only?) regression which is this patch for:
	http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob_plain;f=gdb-6.6-scheduler_locking-step-sw-watchpoints2.patch;hb=f16


Thanks,
Jan


  reply	other threads:[~2011-08-30  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30  1:49 Doug Evans
2011-08-30  9:16 ` Jan Kratochvil [this message]
2011-08-30 10:01   ` pfee
2011-08-30 11:56     ` Jan Kratochvil
2011-08-30 12:42       ` pfee
2011-08-30 14:21         ` Jan Kratochvil
2011-08-30 15:09           ` Doug Evans
2011-08-30 15:22             ` Pedro Alves
2011-08-30 17:13               ` Tom Tromey
2011-08-30 17:29                 ` Pedro Alves
2011-09-02 16:48               ` Doug Evans
2011-08-30 17:00 ` Tom Tromey

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=20110830091623.GA5329@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /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