Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Allow writing to registers before the program starts
Date: Thu, 04 May 2006 09:43:00 -0000	[thread overview]
Message-ID: <4459CBEF.1020808@st.com> (raw)
In-Reply-To: <20060503143952.GA5965@nevyn.them.org>

Daniel Jacobowitz wrote:
> No, this patch is incorrect.  I don't recall exactly why, but I think
> it will mess up writing to the saved registers after using "up".
> I happen to know the actual cause of the problem you're trying to
> fix; there's a nasty hack in CodeSourcery's branch to fix it, but
> the real fix is more work than I've had time for yet.  It's a
> representation problem.

OK, sorry. When I look at it more closely the patch doesn't do quite 
what I thought it did anyway.

This is all much more hideous than I had thought. I don't have either 
the time or the knowledge to fix the problem properly. Thanks for the 
hack - I'll just use that locally for the time-being.

Thanks

Andrew


      reply	other threads:[~2006-05-04  9:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 14:06 Andrew STUBBS
2006-05-03 14:40 ` Daniel Jacobowitz
2006-05-04  9:43   ` Andrew STUBBS [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=4459CBEF.1020808@st.com \
    --to=andrew.stubbs@st.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