From: Nathan Froyd <froydnj@codesourcery.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] persistence of schedlock mode
Date: Mon, 17 May 2010 13:20:00 -0000 [thread overview]
Message-ID: <20100517125656.GN5834@codesourcery.com> (raw)
In-Reply-To: <4BEAEEB0.5040202@vmware.com>
On Wed, May 12, 2010 at 11:08:48AM -0700, Michael Snyder wrote:
> I don't think this is a problem for mode "step", and it could
> be argued that mode "on" is "use at your own risk". However
> I've been thinking about how to resolve it, and this simple
> but intrusive patch is what I come up with.
You should add a declaration for reset_schedlock someplace; otherwise,
you get:
gdb/target.c: In function 'target_mourn_inferior':
gdb/target.c:2249: error: implicit declaration of function 'reset_schedlock'
-Nathan
prev parent reply other threads:[~2010-05-17 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 18:08 Michael Snyder
2010-05-12 19:25 ` Pedro Alves
2010-05-12 19:49 ` Mark Kettenis
2010-05-17 10:33 ` Pierre Muller
2010-05-17 15:29 ` Joel Brobecker
2010-05-17 17:34 ` Michael Snyder
2010-05-17 13:20 ` Nathan Froyd [this message]
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=20100517125656.GN5834@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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