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

[nickc at redhat dot com]

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

--- Comment #10 from Nick Clifton <nickc at redhat dot com> ---
Hi Egon,

(In reply to Egon Elbre from comment #8)

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

Maybe - I could also set up a proper MinGW or Cygwin environment.  The
real problem is time - I just do not have enough of it to spend on these
bugs. :-(

> Do you see the same result with objdump?

Oh yes - I just thought that the non-zero VMA value would be enough.  I did
not know that there was going to be a problem with large gaps between parts
of the program and/or excessively large VMA values.

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

I have gone ahead and done that.  It is a simple, easy fix that will let you
get on with your work for now.

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

Probably.  Although I would love to know if it is the high VMA address that is
causing the problem, or the gap between the two parts of the program that is
causing the problem.  (We are talking 64-bit binaries here, right ?)

Anyway, I will leave this PR open, but I am not expecting to be able to give it
a lot of time unless it becomes a real show-stopper for someone.

Cheers
  Nick

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