[Bug ld/21459] Wrong location for .debug_gdb_scripts on Windows

[egonelbre at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=21459

--- Comment #8 from Egon Elbre <egonelbre at gmail dot com> ---
(In reply to Nick Clifton from comment #7)
> Hi Egon,
> 
> (In reply to Egon Elbre from comment #6)
> > Btw. is there any debug output or any other printf that would be helpful to
> > you?
> 
> No - I can reproduce the problem myself.  I just do not have any way of
> checking whether the binaries produced actually work or not.  Ie I do not
> have a test environment.

I'm wondering whether Wine or ReactOS will fail with that executable?

Do you see the same result with objdump? I guess the VMA should be near the
other sections and when it's not, then it could be considered as broken --
maybe?

> 
> I am wondering whether it would be better to just take the easy way out and
> add .debug_gdb_scripts to the pe and pep linker scripts.  Do you know if
> there are any other .debug_xxx sections that might also be generated for go
> binaries ?

Go - initial searching came up only with:

.debug_abbrev
.debug_aranges
.debug_info
.debug_line
.debug_pubnames
.debug_ranges
.debug_str

Sure, if it seems too much work it's fine to include in the script.

Maybe there's a good place to put an ASSERT bomb when it tries to write VMA >
0xFFFFFFFFLL or zero?

> 
> Cheers
>   Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.