public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18810] internal error in inline_frame_this_id
Date: Sun, 19 Sep 2021 02:52:29 +0000	[thread overview]
Message-ID: <bug-18810-4717-D4eBJVEvCb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18810-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18810

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simark at simark dot ca

--- Comment #4 from Simon Marchi <simark at simark dot ca> ---
(In reply to Sean Anderson from comment #3)
> Hi,
> 
> I am experiencing a similar problem when the stack has been corrupted:
> 
> $ gdb-multiarch vmlinux
> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
> Copyright (C) 2020 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
>     <http://www.gnu.org/software/gdb/documentation/>.
> 
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from vmlinux...
> gdb$ target extended-remote :3333
> Remote debugging using :3333
> memtest (size=<optimized out>, start_phys=<optimized out>,
> pattern=<optimized out>) at mm/memtest.c:49
> 49			*p = pattern;
> gdb$ bt
> #0  memtest (size=<optimized out>, start_phys=<optimized out>,
> pattern=<optimized out>) at mm/memtest.c:49
> #1  do_one_pass (end=<optimized out>, start=<optimized out>,
> pattern=<optimized out>) at mm/memtest.c:78
> #2  early_memtest (/build/gdb-OxeNvS/gdb-9.2/gdb/inline-frame.c:155:
> internal-error: void inline_frame_this_id(frame_info*, void**, frame_id*):
> Assertion `frame_id_p (*this_id)' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> 
> This is a bug, please report it.  For instructions, see:
> <http://www.gnu.org/software/gdb/bugs/>.
> 
> Aborted (core dumped)

Can you please try master + this patch?  It sounds related.

https://sourceware.org/pipermail/gdb-patches/2021-August/181385.html

It might be a bit easier to grab the patch from here:

https://pi.simark.ca/gdb-patches/20210809154122.3468792-1-andrew.burgess@embecosm.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2021-09-19  2:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  3:10 [Bug gdb/18810] New: " sandra at codesourcery dot com
2021-09-10 15:43 ` [Bug gdb/18810] " sean.anderson at seco dot com
2021-09-19  2:52 ` simark at simark dot ca [this message]

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-18810-4717-D4eBJVEvCb@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).