This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Need Help for bringing m68k-based bdm target-patches form gdb-5.2.1 to gdb-5.3


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 --


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]