public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29871] "p tail.y ++ (diff.y / 2)" command causes crash
Date: Tue, 13 Dec 2022 05:03:34 +0000 [thread overview]
Message-ID: <bug-29871-4717-R4pDgv927l@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29871-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29871
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=785545988c222f603a7a190170b04d4b971d7959
commit 785545988c222f603a7a190170b04d4b971d7959
Author: Tom Tromey <tom@tromey.com>
Date: Sun Dec 11 12:48:07 2022 -0700
Fix crash in is_nocall_function
is_nocall_function anticipates only being called for a function or a
method. However, PR gdb/29871 points out a situation where an unusual
expression -- but one that parses to a valid, if extremely weird,
function call -- breaks this assumption.
This patch changes is_nocall_function to remove this assert and
instead simply return 'false' in this case.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29871
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-13 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 21:03 [Bug gdb/29871] New: " georgebateman16 at gmail dot com
2022-12-10 22:30 ` [Bug gdb/29871] " simark at simark dot ca
2022-12-11 19:54 ` tromey at sourceware dot org
2022-12-13 5:03 ` cvs-commit at gcc dot gnu.org [this message]
2022-12-13 5:04 ` tromey at sourceware dot org
2023-03-20 14:45 ` alexandr.miloslavskiy at syntevo 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-29871-4717-R4pDgv927l@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).