[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: egonelbre at gmail dot com
Subject: [Bug ld/21459] Wrong location for .debug_gdb_scripts on Windows
Date: Wed, 10 May 2017 07:38:58 +0000


--- Comment #2 from Egon Elbre <egonelbre at gmail dot com> ---
(In reply to Nick Clifton from comment #1)
> Created attachment 10043 [details]
> Proposed patch
> Hi Egon,
>   Please could you try out this patch ?

I can certainly try :D

But trying to compile anything involving configure and make on Windows has
always been problematic for me.

/Currently in my third hour trying to test it. Managed to finally compile
ld-new, but not quite sure whether I've made a mistake in compiling or invoking
gcc/ld... or the patch wasn't sufficient. I think my mistake is more likely.
But, it does look like it's using new linker and doesn't create a valid
executable. Will investigate further./

>   I think that it should work for debugging sections (ie ones starting with
>   .debug) but it may not solve the general problem of an arbitrary named,
>   non-empty, non-loaded section being placed at VMA 0.

A quick question,

Is there a workaround to coerce the unfixed ld to behave similarly via
command-line flags or some config script?

The best idea we have so far, is to compile with `.xxxxx_gdb_scripts` and then
rename it with `objcopy --rename-section

> Cheers
>   Nick

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]