This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Is nexti confused by pushq?

From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
To: Andrew Burgess <andrew dot burgess at embecosm dot com>
Cc: dwk <dwks42 at gmail dot com>, David Griffiths <dgriffiths at undo dot io>, GDB <gdb at sourceware dot org>
Date: Tue, 26 Feb 2019 11:12:45 +0100
Subject: Re: Is nexti confused by pushq?
References: <CA++j6c4bKPiWgYsSp2ajPLrJmv4wQ6Fb_Z=nXfs7TTOjzAqKRg@mail.gmail.com> <CAPkwjGtoLAPg6dnPOp5fe9-dqFDerhmATESu_wZaUtOOQOp4hA@mail.gmail.com> <20190226073236.GD10887@embecosm.com>

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

Follow-Ups:
- Re: Is nexti confused by pushq?
  - From: David Griffiths

References:
- Is nexti confused by pushq?
  - From: David Griffiths
- Re: Is nexti confused by pushq?
  - From: dwk
- Re: Is nexti confused by pushq?
  - From: Andrew Burgess

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]