PR29617, ld segfaults when bfd_close fails
Alan Modra
amodra@gmail.com
Tue Sep 27 00:44:21 GMT 2022
More information about the Binutils mailing list
Tue Sep 27 00:44:21 GMT 2022
- Previous message (by thread): [PATCH] binutils/testsuite: handle the different install names of c++filt
- Next message (by thread): [PATCH] gdb/arm: Handle lazy FPU register stacking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
PR 29617
* ldmain.c (main): Don't access output_bfd after bfd_close.
diff --git a/ld/ldmain.c b/ld/ldmain.c
index 1bbddaaad32..e676c3786a2 100644
--- a/ld/ldmain.c
+++ b/ld/ldmain.c
@@ -549,7 +549,7 @@ main (int argc, char **argv)
else
{
if (!bfd_close (link_info.output_bfd))
- einfo (_("%F%P: %pB: final close failed: %E\n"), link_info.output_bfd);
+ einfo (_("%F%P: %s: final close failed: %E\n"), output_filename);
/* If the --force-exe-suffix is enabled, and we're making an
executable file and it doesn't end in .exe, copy it to one
--
Alan Modra
Australia Development Lab, IBM
- Previous message (by thread): [PATCH] binutils/testsuite: handle the different install names of c++filt
- Next message (by thread): [PATCH] gdb/arm: Handle lazy FPU register stacking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list