From: Alan Modra <amodra@gmail.com>
To: Mark Harmstone <mark@harmstone.com>
Cc: binutils@sourceware.org, nickc@redhat.com
Subject: Re: [PATCH 01/10] ld: Generate PDB string table
Date: Thu, 22 Dec 2022 20:52:45 +1030 [thread overview]
Message-ID: <Y6Qv9eo7cTdu81sN@squeak.grove.modra.org> (raw)
In-Reply-To: <Y6OyBRoR12KA85qw@squeak.grove.modra.org>
There is also this:
ld/pdb.h:571
/* lfUdtModSrcLine in cvinfo.h */
struct lf_udt_mod_src_line
{
uint16_t size;
uint16_t kind;
uint32_t type;
uint32_t source_file_string;
uint32_t line_no;
uint16_t module_no;
} ATTRIBUTE_PACKED;
ld/pdb.c:2286
memcpy (&umsl->line_no, &usl->line_no, sizeof (uint16_t));
which results in uninitialised data.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-12-22 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 1:52 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 ` [PATCH 03/10] ld: Fix segfault in populate_publics_stream Mark Harmstone
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 [this message]
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=Y6Qv9eo7cTdu81sN@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=mark@harmstone.com \
--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).