From: Josef Wolf <jw@raven.inka.de>
To: Andrew Cagney <ac131313@redhat.com>
Cc: schwab@suse.de, 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: Sun, 10 Aug 2003 21:16:00 -0000 [thread overview]
Message-ID: <20030810211504.GC24206@raven.inka.de> (raw)
In-Reply-To: <3F3505B2.9040104@redhat.com>
On Sat, Aug 09, 2003 at 10:31:14AM -0400, Andrew Cagney wrote:
> Do you have a a copyright ssignment/disclaimer, and do you know who owns
> the code you're working on - can it be contributed to the FSF?
The files claim to be GPL.
> >On Wed, Aug 06, 2003 at 12:09:40PM -0400, Andrew Cagney wrote:
>
> >You are talking about current (pre-6.0) code? Both functions don't exist
> >in 5.3.
> >
> >
> >>(and GDB is desperatly wants to eliminate that hack).
> >
> >
> >Could you please activate verbose mode? Honestly, I did not get what you
> >try to say here. Do you want to eliminate generic_unwind_get_saved_register
> >or frame_register/sentinel_frame_prev_register?
>
> The method register_offset_hack, and the way GDB assumes that a value's
> location can be described by an offset into a register buffer. This
> isn't sufficient. A value may be in multiple registers.
Oh, I see.... But then, what does this mean to porters? What do they need to
do when they want to stay on the bleeding edge of gdb?
--
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-10 21:16 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
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 [this message]
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=20030810211504.GC24206@raven.inka.de \
--to=jw@raven.inka.de \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=schwab@suse.de \
/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