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

2017-05-15 Thread egonelbre at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 --- Comment #11 from Egon Elbre --- (In reply to Nick Clifton from comment #10) > 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

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

2017-05-15 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 --- Comment #10 from Nick Clifton --- 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 prob

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

2017-05-15 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 --- Comment #9 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=786e3eba7915df35df1d98a300e06f757336c75b commit 786e3eba7915df35df1d98a300e

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

2017-05-12 Thread egonelbre at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 --- Comment #8 from Egon Elbre --- (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 rep

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

2017-05-12 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

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

2017-05-11 Thread egonelbre at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 --- Comment #6 from Egon Elbre --- (In reply to Nick Clifton from comment #5) > Created attachment 10046 [details] > Proposed patch > > Updated version of previous patch. Not sure that it will fix the problem of > the excessively large VMA v

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

2017-05-11 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 Nick Clifton changed: What|Removed |Added Attachment #10043|0 |1 is obsolete|

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

2017-05-10 Thread egonelbre at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 --- Comment #4 from Egon Elbre --- (In reply to Nick Clifton from comment #3) > Created attachment 10044 [details] > Linker script fragment > > Hi Egon, > > > But, it does look like it's using new linker and doesn't create a valid > > execu

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

2017-05-10 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 --- Comment #3 from Nick Clifton --- Created attachment 10044 --> https://sourceware.org/bugzilla/attachment.cgi?id=10044&action=edit Linker script fragment Hi Egon, > But, it does look like it's using new linker and doesn't create a valid

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

2017-05-10 Thread egonelbre at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 --- Comment #2 from Egon Elbre --- (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 anyth

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

2017-05-09 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21459 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1