From: Luis Machado <lgustavo@codesourcery.com>
To: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix problems with finishing a dummy function call on simulators.
Date: Mon, 06 Jul 2015 16:18:00 -0000 [thread overview]
Message-ID: <559AAA46.3010607@codesourcery.com> (raw)
In-Reply-To: <559AA992.2020004@redhat.com>
On 07/06/2015 01:15 PM, Pedro Alves wrote:
> On 07/06/2015 04:33 PM, Luis Machado wrote:
>
>> I'll take a look at it. I suppose this will block the branching?
>
> I think so, or at least the release. Broken infcalls seems
> pretty nasty.
>
Indeed.
>> Then again, simply reverting this will still have bad results with some
>> simulators.
>
> True. Might be the fix is simple though. I'm seeing this:
>
> (gdb) PASS: gdb.base/shlib-call.exp: step out of shr2 to main (stopped in shr2 epilogue)
> step
> main () at /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.base/shmain.c:37
> 37 g = mainshr1(g);
> (gdb) PASS: gdb.base/shlib-call.exp: step out of shr2 epilogue to main
> print mainshr1(1)
>
> Program received signal SIGSEGV, Segmentation fault.
> mainshr1 (g=1) at /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.base/shmain.c:29
> 29 }
> The program being debugged was signaled while in a function called from GDB.
> GDB remains in the frame where the signal was received.
> To change this behavior use "set unwindonsignal on".
> Evaluation of the expression containing the function
> (mainshr1) will be abandoned.
> When the function is done executing, GDB will silently stop.
> (gdb) FAIL: gdb.base/shlib-call.exp: print mainshr1(1)
> step
>
That's what i see too.
> The SIGSEGV look scary until one remembers that the dummy breakpoints
> are placed on the stack, which is non-executable. gdb translates those
> SIGSEGVs back to SIGTRAPs, provided it knows there's a breakpoint at that
> address.
>
> Looking a bit at breakpoint.c, I notice that a few ->permanent
> checks seem to have been left behind, and as result we don't actually
> remove from the target the breakpoints that were placed on top of the
> permanent breakpoints?
>
> This seems to fix the FAILs here, but I didn't run full regression
> testing. Could you take this, test it on qemu, and and finish it off?
>
Yes, of course. Thanks for having a go at it.
Luis
next prev parent reply other threads:[~2015-07-06 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 15:01 Luis Machado
2015-06-09 17:51 ` Pedro Alves
2015-06-09 18:10 ` Luis Machado
2015-06-09 18:13 ` Pedro Alves
2015-06-09 18:22 ` Luis Machado
2015-06-09 18:34 ` Luis Machado
2015-06-16 17:39 ` Luis Machado
2015-06-17 12:41 ` Pedro Alves
2015-06-17 13:26 ` Luis Machado
2015-06-17 13:43 ` Pedro Alves
2015-06-17 20:16 ` Luis Machado
2015-07-06 15:06 ` Pedro Alves
2015-07-06 15:33 ` Luis Machado
2015-07-06 16:15 ` Pedro Alves
2015-07-06 16:18 ` Luis Machado [this message]
2015-07-06 18:34 ` Luis Machado
2015-07-06 19:07 ` Pedro Alves
2015-07-06 19:11 ` Luis Machado
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=559AAA46.3010607@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--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