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 gdb/29941] Inferior call strlen(p) gives segfaults in GDB 13, (somewhat?) works in GDB11 and GDB12 Date: Mon, 26 Dec 2022 07:39:47 +0000 [thread overview] Message-ID: <bug-29941-4717-ehbjzBaq4l@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29941-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29941 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vries at gcc dot gnu.org --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- This seems to fix it: ... diff --git a/gdb/infcall.c b/gdb/infcall.c index c1db3e22189..9bfc3216c5a 100644 --- a/gdb/infcall.c +++ b/gdb/infcall.c @@ -857,6 +857,7 @@ call_function_by_hand_dummy (struct value *function, type *ftype; type *values_type; CORE_ADDR funaddr = find_function_addr (function, &values_type, &ftype); + frame = get_current_frame (); if (is_nocall_function (ftype)) error (_("Cannot call the function '%s' which does not follow the " ... Note that during find_function_addr, a call to call_function_by_hand_dummy is done for elf_gnu_ifunc_resolve_addr, which pushes and pops a dummy frame. I don't understand the frame tracking concepts well enough to say whether this is a fix or a workaround. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-26 7:39 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-25 20:47 [Bug gdb/29941] New: " philippe.waroquiers at skynet dot be 2022-12-25 23:37 ` [Bug gdb/29941] " mark at klomp dot org 2022-12-26 7:39 ` vries at gcc dot gnu.org [this message] 2022-12-26 12:59 ` aburgess at redhat dot com 2022-12-26 13:08 ` vries at gcc dot gnu.org 2023-01-03 9:18 ` cvs-commit at gcc dot gnu.org 2023-01-03 10:53 ` cvs-commit 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-29941-4717-ehbjzBaq4l@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: linkBe 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).