From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/25831] Assertion failure in eu-objdump
Date: Thu, 16 Apr 2020 13:54:29 +0000 [thread overview]
Message-ID: <bug-25831-10460-lRI4u3M1VQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25831-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25831
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2020-04-16
CC| |mark at klomp dot org
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
It is bad code and so correct to reject it. But we can reject it without
asserting and just printing "(bad)". Proposed patch:
https://sourceware.org/pipermail/elfutils-devel/2020q2/002619.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-16 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 6:28 [Bug general/25831] New: " nguyenmanhdung1710 at gmail dot com
2020-04-16 13:54 ` mark at klomp dot org [this message]
2020-04-21 20:29 ` [Bug general/25831] " mark at klomp dot org
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=bug-25831-10460-lRI4u3M1VQ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).