From: David Griffiths <dgriffiths@undo.io>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
dwk <dwks42@gmail.com>, GDB <gdb@sourceware.org>
Subject: Re: Is nexti confused by pushq?
Date: Tue, 26 Feb 2019 11:50:00 -0000 [thread overview]
Message-ID: <CA++j6c7=KNZgErDbEyEi81MUAVwYKeDC8dfPxGT_w=EBqUzNsA@mail.gmail.com> (raw)
In-Reply-To: <20190226101245.GA1496753@host1.jankratochvil.net>
Ok, so in my case this is generated code with no debug info (Java JIT
generated) so does that mean I shouldn't attempt to use nexti? (I've got
other issues which probably preclude using nexti anyway but just curious)
Cheers,
David
On Tue, 26 Feb 2019 at 10:12, Jan Kratochvil <jan.kratochvil@redhat.com>
wrote:
> On Tue, 26 Feb 2019 08:32:37 +0100, Andrew Burgess wrote:
> > Of course, this doesn't solve the problem for you, but at least you
> > know what's going wrong now :)
>
> To make it clear the debuggee has wrong/insufficient debug info, its
> .eh_frame/.debug_frame there should annotate the push (and pop)
> instructions.
>
>
> Jan
>
--
David Griffiths, Senior Software Engineer
Undo <https://undo.io> | Resolve even the most challenging software defects
with software flight recorder technology
Software reliability report: optimizing the software supplier and customer
relationship
<https://info.undo.io/software-reliability-report-optimizing-supplier-and-customer-relationship>
next prev parent reply other threads:[~2019-02-26 11:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 15:40 David Griffiths
2019-02-25 15:54 ` dwk
2019-02-26 7:32 ` Andrew Burgess
2019-02-26 10:12 ` Jan Kratochvil
2019-02-26 11:50 ` David Griffiths [this message]
2019-02-26 11:58 ` Jan Kratochvil
2019-02-26 14:19 ` Dmitry Samersoff
2019-02-26 14:42 ` David Griffiths
2019-02-26 19:05 ` Tom Tromey
2019-02-27 7:59 ` Dmitry Samersoff
2019-02-27 14:53 ` Tom Tromey
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='CA++j6c7=KNZgErDbEyEi81MUAVwYKeDC8dfPxGT_w=EBqUzNsA@mail.gmail.com' \
--to=dgriffiths@undo.io \
--cc=andrew.burgess@embecosm.com \
--cc=dwks42@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).