https://sourceware.org/bugzilla/show_bug.cgi?id=23906
Tamar Christina <tnfchris at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tnfchris at sourceware dot org
--- Comment #10 from Tamar Christina <tnfchris at sourceware dot org> ---
Hi David,
I have tried to reproduce this today using the files you provided and it seems
to work fine.
C:\Users\tamar\Desktop\binutils\Release>arm-none-eabi-g++ -mcpu=cortex-m0
-march=armv6-m -mthumb -Os -fmessage-length=0 -ffunction-sections
-fdata-sections -ffreestanding -Wall -Wextra -g -T "../ldscripts/mem.ld" -T
"../ldscripts/sections.ld" -T "../ldscripts/libs.ld" -nostartfiles -Xlinker
--gc-sections -L"../ldscripts" <snip>
GNU ld (GNU Tools for Arm Embedded Processors 7-2018-q2-update) 2.30.0.20180329
PS C:\Users\tamar\Desktop\binutils\Release> echo $LASTEXITCODE
0
PS C:\Users\tamar\Desktop\binutils\Release> dir *.elf
Directory: C:\Users\tamar\Desktop\binutils\Release
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 12/10/2018 1:05 PM 6117116 uSupply Firmware V1_0.elf
Since gdb doesn't support coredumps on Windows, can you instead get a windbg
dump using procdump?
https://docs.microsoft.com/en-us/sysinternals/downloads/procdump
using
procdump.exe -t -ma -e 1 -x . <prog+args>
which will dump the entire process memory.
Unfortunately procdump can't dump child processes so you'll have to isolate the
linker command from g++,
you can do this by running g++ with -Wl,-debug -save-temps as Nick mentioned
before.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
