public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: Need help with understanding truncated and corrupted backtraces
Date: Fri, 26 Mar 2021 10:19:44 +0300	[thread overview]
Message-ID: <835z1eqt4f.fsf@gnu.org> (raw)
In-Reply-To: <340a8bb9-87f8-1b37-7ba9-8d497535642e@polymtl.ca> (message from Simon Marchi on Thu, 25 Mar 2021 10:19:53 -0400)

> Cc: gdb-patches@sourceware.org
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Date: Thu, 25 Mar 2021 10:19:53 -0400
> 
> It would be interesting to see the output of your two backtraces, with
> "set debug frame 1" enabled (with my patches applied).

OK, I will build a snapshot of the master branch with your patches,
and get back with that info.

Thanks.

  reply	other threads:[~2021-03-26  7:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 13:24 Eli Zaretskii
2021-03-24 20:05 ` Eli Zaretskii
2021-03-24 22:48 ` Simon Marchi
2021-03-25  3:47   ` Simon Marchi
2021-03-25 10:09     ` Eli Zaretskii
2021-03-25 14:19       ` Simon Marchi
2021-03-26  7:19         ` Eli Zaretskii [this message]
2021-03-29  8:03         ` Eli Zaretskii
2021-03-29 14:33           ` Simon Marchi
2021-03-29 14:57             ` Eli Zaretskii
2021-03-29 15:32               ` Simon Marchi
2021-03-29 15:37                 ` Eli Zaretskii
2021-03-29 15:39                   ` Simon Marchi
2021-03-29 16:55                     ` Eli Zaretskii
2021-03-29 17:13                       ` Simon Marchi
2021-04-06 15:18                 ` Eli Zaretskii
2021-03-25 10:04   ` Eli Zaretskii

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=835z1eqt4f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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).