From: Samuel Hym <samuel.hym+bugs@rustyne.lautre.net>
To: overseers@sourceware.org
Subject: New account to report a bug in ld
Date: Mon, 11 Jul 2022 22:34:23 +0200 [thread overview]
Message-ID: <YsyJT9Hv/T8jSnR+@munk.lifl.fr> (raw)
Hi,
We encountered a segfault in ld and built a minimal example to
reproduce the bug. Could I get a bugzilla account to report it?
Alternatively, I can report it in the debian bug tracker, but I could
also reproduce the bug in alpine, so I’m pretty sure it’s a bug from
upstream.
Best regards,
--
Samuel Hym
next reply other threads:[~2022-07-11 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 20:34 Samuel Hym [this message]
2022-07-11 20:39 ` Mark Wielaard
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=YsyJT9Hv/T8jSnR+@munk.lifl.fr \
--to=samuel.hym+bugs@rustyne.lautre.net \
--cc=overseers@sourceware.org \
/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).