From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: wingo@igalia.com, gdb-patches@sourceware.org, asmundak@google.com
Subject: Re: [PATCH v2] Add Guile frame unwinder interface
Date: Mon, 09 Mar 2015 16:22:00 -0000 [thread overview]
Message-ID: <83mw3m5efm.fsf@gnu.org> (raw)
In-Reply-To: <54FDBF21.4090400@redhat.com>
> Date: Mon, 09 Mar 2015 15:41:21 +0000
> From: Pedro Alves <palves@redhat.com>
> CC: asmundak@google.com
>
> >From a glimpse over the code, I think this actually marks it as
> "<not saved>" (optimized out), right? That would be the correct
> thing to do. Marking a register as "<unavailable>" is also possible,
> but it is a different thing -- it means the value exists, but gdb
> couln't get to it, because e.g., the core file is trimmed, or the
> ptrace interface is missing access to some registers.
Actually, from past discussions I understand that "optimized out" more
often than not means "value exists, but GDB is not smart enough to
interpret the DWARF info to find it and/or GCC didn't put enough of
the info there to begin with". So I wish we would at some point says
something different when this is the case, instead of hiding behind
unnamed "optimizations".
next prev parent reply other threads:[~2015-03-09 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 15:58 [PATCH] " Andy Wingo
2015-03-09 10:34 ` [PATCH v2] " Andy Wingo
2015-03-09 15:42 ` Pedro Alves
2015-03-09 16:22 ` Eli Zaretskii [this message]
2015-03-09 18:54 ` Andy Wingo
2015-03-10 9:03 ` [PATCH v3] " Andy Wingo
2015-03-10 17:48 ` Doug Evans
2015-03-11 9:33 ` Andy Wingo
2015-03-10 15:46 ` [PATCH v2] " Pedro Alves
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=83mw3m5efm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=asmundak@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=wingo@igalia.com \
/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