From: Mark Harmstone <mark@harmstone.com>
To: binutils@sourceware.org, nickc@redhat.com
Cc: Mark Harmstone <mark@harmstone.com>
Subject: [PATCH 03/10] ld: Fix segfault in populate_publics_stream
Date: Fri, 9 Dec 2022 01:52:33 +0000 [thread overview]
Message-ID: <20221209015240.6348-3-mark@harmstone.com> (raw)
In-Reply-To: <20221209015240.6348-1-mark@harmstone.com>
---
ld/pdb.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/ld/pdb.c b/ld/pdb.c
index b37a5a0ebfd..3edeab25332 100644
--- a/ld/pdb.c
+++ b/ld/pdb.c
@@ -1410,6 +1410,9 @@ populate_publics_stream (bfd *stream, bfd *abfd, bfd *sym_rec_stream)
for (bfd *in = coff_data (abfd)->link_info->input_bfds; in;
in = in->link.next)
{
+ if (!in->outsymbols)
+ continue;
+
for (unsigned int i = 0; i < in->symcount; i++)
{
struct bfd_symbol *sym = in->outsymbols[i];
--
2.37.4
next prev parent reply other threads:[~2022-12-09 1:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 1:52 [PATCH 01/10] ld: Generate PDB string table Mark Harmstone
2022-12-09 1:52 ` [PATCH 02/10] ld: Write DEBUG_S_FILECHKSMS entries in PDBs Mark Harmstone
2022-12-09 1:52 ` Mark Harmstone [this message]
2022-12-09 1:52 ` [PATCH 04/10] ld: Write DEBUG_S_LINES entries in PDB file Mark Harmstone
2022-12-09 1:52 ` [PATCH 05/10] ld: Write types into TPI stream of PDB Mark Harmstone
2022-12-09 1:52 ` [PATCH 06/10] ld: Write types into IPI " Mark Harmstone
2022-12-09 1:52 ` [PATCH 07/10] ld: Parse LF_UDT_SRC_LINE records when creating PDB file Mark Harmstone
2022-12-09 1:52 ` [PATCH 08/10] ld: Write globals stream in PDB Mark Harmstone
2022-12-09 1:52 ` [PATCH 09/10] ld: Copy other symbols into PDB file Mark Harmstone
2022-12-09 1:52 ` [PATCH 10/10] ld: Write linker symbols in PDB Mark Harmstone
2022-12-22 0:05 ` [PATCH 01/10] ld: Generate PDB string table Alan Modra
2022-12-22 1:25 ` Alan Modra
2022-12-22 10:22 ` Alan Modra
2022-12-23 10:54 ` Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221209015240.6348-3-mark@harmstone.com \
--to=mark@harmstone.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).