From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Toshihito Kikuchi <k.toshihito@yahoo.de>
Cc: "Paul_Koning@Dell.com" <Paul_Koning@Dell.com>,
"palves@redhat.com" <palves@redhat.com>,
"jhb@freebsd.org" <jhb@freebsd.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add a new format letter to dump instructions backward
Date: Wed, 27 Jan 2016 16:04:00 -0000 [thread overview]
Message-ID: <20160127160420.GM3338@embecosm.com> (raw)
In-Reply-To: <1095889805.138513.1453786618993.JavaMail.yahoo@mail.yahoo.com>
* Toshihito Kikuchi <k.toshihito@yahoo.de> [2016-01-26 05:36:58 +0000]:
> To answer the question from Paul, Pedro's guess is correct. I used
> symbol's line info to solve a correct frame. And yes, this feature
> does not work without debug information unfortunately.
If there's no debug information then just looking for symbols in the
same section would also be a reasonable guess. Most symbols appear
between instructions, not part way through an instruction.
Sounds like a useful feature.
Thanks,
Andrew
next prev parent reply other threads:[~2016-01-27 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1827952218.466587.1453670934999.JavaMail.yahoo.ref@mail.yahoo.com>
2016-01-24 21:31 ` Toshihito Kikuchi
2016-01-25 11:41 ` Pedro Alves
2016-01-25 18:10 ` John Baldwin
2016-01-25 18:22 ` Paul_Koning
2016-01-25 18:27 ` Pedro Alves
2016-01-25 20:11 ` Paul_Koning
2016-01-26 5:39 ` Toshihito Kikuchi
2016-01-27 16:04 ` Andrew Burgess [this message]
2016-01-27 20:09 ` Paul_Koning
2016-01-28 11:53 ` Pedro Alves
2016-02-07 23:19 ` [PATCH] Negative repeat count for 'x' command Toshihito Kikuchi
2016-02-17 11:38 ` Pedro Alves
2016-03-23 0:27 ` Toshihito Kikuchi
2016-04-11 12:17 ` Pedro Alves
2016-04-15 0:30 ` Toshihito Kikuchi
[not found] ` <5714DE73.5010104@redhat.com>
2016-04-28 18:06 ` Toshihito Kikuchi
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=20160127160420.GM3338@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=Paul_Koning@Dell.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=k.toshihito@yahoo.de \
--cc=palves@redhat.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