From: "Shaun Jackman" <sjackman@gmail.com>
To: gdb@sources.redhat.com
Subject: Re: Modifying a verboten register
Date: Fri, 29 Feb 2008 18:22:00 -0000 [thread overview]
Message-ID: <7f45d9390802291019o762c6bcby57e88f4134ae510e@mail.gmail.com> (raw)
In-Reply-To: <20080229134004.GA2573@caradoc.them.org>
On Fri, Feb 29, 2008 at 5:40 AM, Daniel Jacobowitz <drow@false.org> wrote:
> On Thu, Feb 28, 2008 at 08:37:58PM -0800, Shaun Jackman wrote:
> > Was this patch ever applied to the trunk? I've just checked that the
> > bug still exists in gdb 6.7. The above patch was from 2006-July circa
> > gdb 6.5 days.
>
> That patch will not be applied; as I mentioned at the time, it's a
> nasty hack. Unfortunately, no one has had time to work on this
> problem.
Okay. Well, thanks for the hack in any case.
Cheers,
Shaun
prev parent reply other threads:[~2008-02-29 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 14:45 Shaun Jackman
2006-05-04 14:52 ` Daniel Jacobowitz
2006-05-04 15:15 ` Shaun Jackman
2006-07-12 23:16 ` Shaun Jackman
2008-02-29 11:13 ` Shaun Jackman
2008-02-29 13:41 ` Daniel Jacobowitz
2008-02-29 18:22 ` Shaun Jackman [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=7f45d9390802291019o762c6bcby57e88f4134ae510e@mail.gmail.com \
--to=sjackman@gmail.com \
--cc=gdb@sources.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