public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@yahoo.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	 Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH] Fix backtrace limit stopping on inline frame
Date: Mon, 29 Jan 2024 14:35:24 +0000 (UTC)	[thread overview]
Message-ID: <2117166582.3585768.1706538924442@mail.yahoo.com> (raw)
In-Reply-To: <87v87cxvck.fsf@redhat.com>

 Am Montag, 29. Januar 2024 um 11:55:14 MEZ hat Andrew Burgess <aburgess@redhat.com> Folgendes geschrieben:

> Hannes Domani <ssbssa@yahoo.de> writes:
>
> > If you have set up a backtrace limit, and the backtrace stops
> > because of this in an inline frame with arguments, you get an
> > assertion failure:
> > ```
> > (gdb) bt
> > #0  normal_frame (i=0) at gdb-29865.c:4
> > #1  0x000000013fe3162a in inline_frame (i=0) at gdb-29865.c:9
> > #2  main () at gdb-29865.c:14
> > (gdb) set backtrace limit 2
> > (gdb) bt
> > #0  normal_frame (i=0) at gdb-29865.c:4
> > #1  0x000000013fe3162a in inline_frame (
> > C:/src/repos/binutils-gdb.git/gdb/frame.c:3346: internal-error: reinflate: Assertion `m_cached_level >= -1' failed.
> > ```
> >
> > And if this one if fixed, there is another one as well:
>
> s/one if fixed/one is fixed/.
>
> Otherwise, looks good.  Thanks for fixing this.
>
> Approved-By: Andrew Burgess <aburgess@redhat.com>

Pushed with this typo fixed, thanks.


Hannes

      reply	other threads:[~2024-01-29 14:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240106141735.2330-1-ssbssa.ref@yahoo.de>
2024-01-06 14:17 ` Hannes Domani
2024-01-17 16:05   ` [PING] " Hannes Domani
2024-01-26 17:05     ` Hannes Domani
2024-01-29 10:55   ` Andrew Burgess
2024-01-29 14:35     ` Hannes Domani [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=2117166582.3585768.1706538924442@mail.yahoo.com \
    --to=ssbssa@yahoo.de \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@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).