From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb@sources.redhat.com
Subject: Re: Frame lost after 'leave' and before 'ret' instruction on i386?
Date: Fri, 23 May 2008 15:19:00 -0000 [thread overview]
Message-ID: <4835989F.3090900@qnx.com> (raw)
In-Reply-To: <20080522150458.GA1274@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Thu, May 22, 2008 at 10:51:12AM -0400, Aleksandar Ristovski wrote:
>> So from what I can see, they all rely on symbol info (find_pc_partial_function).
>
> Generally, so that you don't go marching off into the code of another
> function. If you only look at instructions forwards, and do not skip
> any branches, you can probably do without it.
>
Am I again missing something big or is this really being called only from breakpoint.c?
I would imagine it should be called from other spots as well. I find handle_inferior_status quite complicated and do not fully understand it, but shouldn't it be called from there as well (when stepi-ing, we need to know if the frame can be created or not).
WARNING: multiple messages have this Message-ID
From: Aleksandar Ristovski <aristovski@qnx.com>
To: Daniel Jacobowitz <drow@false.org>, gdb@sourceware.org
Subject: Re: Frame lost after 'leave' and before 'ret' instruction on i386?
Date: Thu, 22 May 2008 18:06:00 -0000 [thread overview]
Message-ID: <4835989F.3090900@qnx.com> (raw)
Message-ID: <20080522180600.DWsOtHoVFK_ms7v1s3vtQJWuVZeKf07Jj8qQxj-HNDI@z> (raw)
In-Reply-To: <20080522150458.GA1274@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Thu, May 22, 2008 at 10:51:12AM -0400, Aleksandar Ristovski wrote:
>> So from what I can see, they all rely on symbol info (find_pc_partial_function).
>
> Generally, so that you don't go marching off into the code of another
> function. If you only look at instructions forwards, and do not skip
> any branches, you can probably do without it.
>
Am I again missing something big or is this really being called only from breakpoint.c?
I would imagine it should be called from other spots as well. I find handle_inferior_status quite complicated and do not fully understand it, but shouldn't it be called from there as well (when stepi-ing, we need to know if the frame can be created or not).
next prev parent reply other threads:[~2008-05-22 16:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 15:32 Aleksandar Ristovski
2008-05-16 15:58 ` Daniel Jacobowitz
2008-05-16 16:02 ` Aleksandar Ristovski
2008-05-16 16:09 ` Daniel Jacobowitz
2008-05-22 14:29 ` Aleksandar Ristovski
2008-05-22 14:40 ` Aleksandar Ristovski
2008-05-22 14:50 ` Daniel Jacobowitz
2008-05-22 15:05 ` Aleksandar Ristovski
2008-05-22 16:00 ` Aleksandar Ristovski
2008-05-22 16:02 ` Daniel Jacobowitz
2008-05-23 15:19 ` Aleksandar Ristovski [this message]
2008-05-22 18:06 ` Aleksandar Ristovski
2008-05-23 17:11 ` Daniel Jacobowitz
2008-05-23 17:23 ` Michael Snyder
2008-05-26 23:08 ` Aleksandar Ristovski
2008-05-27 21:33 ` Aleksandar Ristovski
2008-05-29 6:21 ` Thiago Jung Bauermann
2008-05-29 6:22 ` Aleksandar Ristovski
2008-06-04 13:12 ` Aleksandar Ristovski
2008-06-05 20:12 ` Mark Kettenis
2008-05-16 17:24 ` Mark Kettenis
2008-05-16 17:28 ` Aleksandar Ristovski
2008-05-16 17:47 ` Daniel Jacobowitz
2008-05-16 17:48 ` Mark Kettenis
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=4835989F.3090900@qnx.com \
--to=aristovski@qnx.com \
--cc=gdb@sources.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