On Fri, 17 Jan 2003, Richard Henderson wrote:
> On Fri, Jan 17, 2003 at 11:49:01PM +0100, Fabio Alemagna wrote:
> > Wait a minute, are you saying IA-64 implements section-relative
> > relocations? Is that for any kind of sections, or just the dwarf's ones?
>
> Any sections. See R_IA64_SECREL* i
On Fri, Jan 17, 2003 at 11:49:01PM +0100, Fabio Alemagna wrote:
> Wait a minute, are you saying IA-64 implements section-relative
> relocations? Is that for any kind of sections, or just the dwarf's ones?
Any sections. See R_IA64_SECREL* in bfd/elfxx-ia64.c.
r~
--
Unsubscribe info: http:/
Yup. That's what the main said.
Look at the pseudo op @secrel().
If you figure out how to implement this for AROS, I'd love any additional
insight you can share. I'm currently blindly stubling in gas and bfd.
On Fri, 17 Jan 2003, Fabio Alemagna wrote:
> On Fri, 17 Jan 2003, Richard Henderson
On Fri, 17 Jan 2003, Richard Henderson wrote:
> On Thu, Jan 16, 2003 at 09:18:20AM -0600, Brian Ford wrote:
> > I am still consulting the DWARF2 spec to see if gcc and gas are
> > correct in generating VMA addresses. If so, I guess I have to fix the
> > dwarf parsing code in bfd and gdb to subtra
Thanks for the response. I came to that ugly conclusion yesterday.
On Fri, 17 Jan 2003, Richard Henderson wrote:
> No, dwarf specifies a section-relative address. The issue is that,
> with the exception of IA-64, no target has section-relative relocations.
> So instead we force the VMA to zero
On Thu, Jan 16, 2003 at 09:18:20AM -0600, Brian Ford wrote:
> I am still consulting the DWARF2 spec to see if gcc and gas are
> correct in generating VMA addresses. If so, I guess I have to fix the
> dwarf parsing code in bfd and gdb to subtract the section base VMA.
No, dwarf specifies a section
On Thu, 16 Jan 2003, Christopher Faylor wrote:
> On Thu, Jan 16, 2003 at 03:58:09PM +, Nick Clifton wrote:
> >Does the PE format require that the debugging sections be loaded into
> >memory when the executable is invoked ?
>
> I didn't think that STABS debug information was loaded into memory.
On 16 Jan 2003, Nick Clifton wrote:
> Hi Brian,
>
> > My current problem is that all previous DWARF2 implementations
> > assign a VMA of zero to the .debug_* sections in the link script.
> > This violates the PE format and makes the executable unusable.
>
> I saw your post about this to the binuti
On Thu, Jan 16, 2003 at 03:58:09PM +, Nick Clifton wrote:
>Hi Brian,
>
>> My current problem is that all previous DWARF2 implementations
>> assign a VMA of zero to the .debug_* sections in the link script.
>> This violates the PE format and makes the executable unusable.
>
>I saw your post abou
Hi Brian,
> My current problem is that all previous DWARF2 implementations
> assign a VMA of zero to the .debug_* sections in the link script.
> This violates the PE format and makes the executable unusable.
I saw your post about this to the binutils list.
Does the PE format require that the deb
On 16 Jan 2003, Nick Clifton wrote:
> Hi Brian,
>
> > The coff versions of sec_to_styp_flags and styp_to_sec_flag in bfd
> > look to see if the section name begins with .debug and modify the
> > section flags appropriately. The PE versions do not even look at
> > the section name.
>
> Ahh, yes, y
Hi Brian,
> The coff versions of sec_to_styp_flags and styp_to_sec_flag in bfd
> look to see if the section name begins with .debug and modify the
> section flags appropriately. The PE versions do not even look at
> the section name.
Ahh, yes, you are right. I guess that no-one has tried to
inc
On 14 Jan 2003, Nick Clifton wrote:
> Hi Brian,
>
> > I have built gcc 3.2.1 (just --enable-languages=c so far) with
> > "#define DWARF2_DEBUGGING_INFO 1" added to config/i386/cygwin.h.
> > The resulting compiler still produces stabs by default, but will
> > accept "-gdwarf-2".
> >
> > When using
Hi Brian,
> I have built gcc 3.2.1 (just --enable-languages=c so far) with
> "#define DWARF2_DEBUGGING_INFO 1" added to config/i386/cygwin.h.
> The resulting compiler still produces stabs by default, but will
> accept "-gdwarf-2".
>
> When using "-gdwarf-2", the debug information is, I believe,
>
Please CC me on replys. I am not currently subscribed to any of these
lists.
I am interested in contributing to this endeavor, but I need help
with a few specific problems. Any pointers or information about known
issues would be greatly appreciated.
I have built gcc 3.2.1 (just --enable-languag
15 matches
Mail list logo