public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/25565] gdb step will falsely exit for calling malloc function
Date: Sun, 03 Jan 2021 07:43:36 +0000 [thread overview]
Message-ID: <bug-25565-4717-BhZUzq9d5e@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25565-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25565
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Yibiao Yang from comment #2)
> (In reply to Tom de Vries from comment #1)
> > I tried with gcc 9.3.1, and both gdb trunk and gdb-10-branch. Can't
> > reproduce.
> >
> > Does this reproduce for you with either gdb trunk, or gdb-10-branch (or,
> > gdb-10.1-release if that's easier for you)?
>
> Yes, this unexpected behavior is observed in the GNU gdb version of (GDB)
> 9.0.50.20191210-git.
The version you mention is neither gdb-10-branch, nor current trunk.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-03 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25565-4717@http.sourceware.org/bugzilla/>
2020-05-27 21:02 ` [Bug symtab/25565] gdb step will falsely exit for malloc function call statement when compiled with "--coverage" option yangyibiao at hust dot edu.cn
2020-12-28 8:28 ` yangyibiao at outlook dot com
2020-12-28 8:31 ` [Bug symtab/25565] gdb step will falsely exit for calling malloc function yangyibiao at outlook dot com
2020-12-28 8:31 ` [Bug gdb/25565] " yangyibiao at outlook dot com
2020-12-30 2:32 ` [Bug breakpoints/25565] " yangyibiao at outlook dot com
2020-12-30 16:36 ` vries at gcc dot gnu.org
2021-01-03 6:55 ` yangyibiao at outlook dot com
2021-01-03 7:43 ` vries at gcc dot gnu.org [this message]
2021-01-06 12:28 ` vries at gcc dot gnu.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-25565-4717-BhZUzq9d5e@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).