From: Josef Wolf <jw@raven.inka.de>
To: gdb@sources.redhat.com
Subject: Re: Need Help for bringing m68k-based bdm target-patches form gdb-5.2.1 to gdb-5.3
Date: Tue, 05 Aug 2003 21:50:00 -0000 [thread overview]
Message-ID: <20030805214938.GA26288@raven.inka.de> (raw)
In-Reply-To: <20030731223514.GD20282@raven.inka.de>
Hello!
On Fri, Aug 01, 2003 at 12:35:14AM +0200, Josef Wolf wrote:
Could it be that noone have noticed my first mail? IMHO, at least this:
[ ... ]
> The relevant change was that default_get_saved_register() was deleted
> and replaced with generic_unwind_get_saved_register()
>
> The problem with this replacement was that default_get_saved_register()
> semantically did
>
> if (frame==NULL)
> *addrp=REGISTER_BYTE(regnum);
>
> while generic_unwind_get_saved_register() semantically did
>
> if (frame==NULL)
> *addrp=0;
>
> This confused value_of_register() because it stores this address into
> the value struct, so that callers can calculate the register number from
> this address. This results in clobbering of all the register contents of
> the target because everything seemed to be in register 0.
seems to be a bug in gdb. And this bug is still present in gdb-5.3. Maybe
one of the gdb-gurus could clarify this?
--
Please visit and sign http://petition-eurolinux.org and http://www.ffii.org
-- Josef Wolf -- jw@raven.inka.de --
next prev parent reply other threads:[~2003-08-05 21:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 22:36 Josef Wolf
2003-08-05 21:50 ` Josef Wolf [this message]
2003-08-06 16:09 ` Andrew Cagney
2003-08-06 22:17 ` Josef Wolf
2003-08-09 14:31 ` Andrew Cagney
2003-08-10 21:16 ` Josef Wolf
2003-08-06 18:22 ` Andreas Schwab
2003-08-06 20:55 ` Josef Wolf
2003-08-07 6:08 ` Andreas Schwab
2003-08-07 14:35 ` Andrew Cagney
2003-08-10 20:59 ` Josef Wolf
2003-08-10 20:48 ` Josef Wolf
2003-08-11 9:36 ` Andreas Schwab
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=20030805214938.GA26288@raven.inka.de \
--to=jw@raven.inka.de \
--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