From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30959] abidiff segfault on function call expression considered malformed
Date: Wed, 11 Oct 2023 11:24:25 +0000 [thread overview]
Message-ID: <bug-30959-9487-aCHWLaLoJt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30959-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30959
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|abidiff segfault with |abidiff segfault on
|certain regex patterns |function call expression
| |considered malformed
--- Comment #1 from dodji at redhat dot com ---
This issue should be fixed by the
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-11 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 16:43 [Bug default/30959] New: abidiff segfault with certain regex patterns quic_johmoo at quicinc dot com
2023-10-11 11:06 ` [Bug default/30959] " dodji at redhat dot com
2023-10-11 11:24 ` dodji at redhat dot com [this message]
2023-10-11 12:10 ` [Bug default/30959] abidiff segfault on function call expression considered malformed dodji at redhat dot com
2023-10-11 17:24 ` quic_johmoo at quicinc dot com
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-30959-9487-aCHWLaLoJt@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@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).