public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
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 15:33:00 -0000	[thread overview]
Message-ID: <559A9FCE.5070908@codesourcery.com> (raw)
In-Reply-To: <559A998E.6010500@redhat.com>

On 07/06/2015 12:06 PM, Pedro Alves wrote:
> Hi Luis,
>
> Looks like this regressed gdbserver somehow.
>
> On 06/17/2015 09:16 PM, Luis Machado wrote:
>> On 06/17/2015 10:43 AM, Pedro Alves wrote:
>>> On 06/17/2015 02:26 PM, Luis Machado wrote:
>>>> On 06/17/2015 09:40 AM, Pedro Alves wrote:
>>>
>>>>> Yep.  Close, but also remove the bp_call_dummy check in
>>>>> bp_loc_is_permanent, and merge in its comment, like ...
>>>>>
>>>>
>>>> Fixed now.
>>>
>>> Looks good now.  Thanks.
>>>
>>>> The attached updated patch also removes this dead function. I can commit
>>>> it as a separate patch if you're not removing it yourself.
>>>
>>> Nah, I was hoping you'd remove it.  :-)  Please also remove the
>>> make_breakpoint_permanent declaration from breakpoint.h though.
>>
>> Thanks. I've pushed this in now and pushed the removal with a different
>> patch.
>>
>
> Compared to before the patch, I see these:
>
> -PASS: gdb.base/shlib-call.exp: print mainshr1(1)
> -PASS: gdb.base/shlib-call.exp: step into mainshr1
> +FAIL: gdb.base/shlib-call.exp: print mainshr1(1)
> +FAIL: gdb.base/shlib-call.exp: step into mainshr1
>   PASS: gdb.base/shlib-call.exp: set print sevenbit-strings
>   PASS: gdb.cp/chained-calls.exp: g(f())
> -PASS: gdb.cp/chained-calls.exp: q(p())
> +FAIL: gdb.cp/chained-calls.exp: q(p())
>   PASS: gdb.cp/chained-calls.exp: p() + r()
> -PASS: gdb.cp/chained-calls.exp: q(p() + r())
> +FAIL: gdb.cp/chained-calls.exp: q(p() + r())
>   PASS: gdb.cp/chained-calls.exp: g(f() + f())
> -PASS: gdb.cp/chained-calls.exp: g(f(g(f() + f())) + f())
> +FAIL: gdb.cp/chained-calls.exp: g(f(g(f() + f())) + f())
>   PASS: gdb.cp/chained-calls.exp: getb(makeb(), ...)
> -PASS: gdb.cp/chained-calls.exp: *c
> -PASS: gdb.cp/chained-calls.exp: *c + *c
> -PASS: gdb.cp/chained-calls.exp: q(*c + *c)
> +FAIL: gdb.cp/chained-calls.exp: *c
> +FAIL: gdb.cp/chained-calls.exp: *c + *c
> +FAIL: gdb.cp/chained-calls.exp: q(*c + *c)
>
>   PASS: gdb.cp/classes.exp: print cnsi with static members
>   PASS: gdb.cp/classes.exp: finish from marker_reg1
> -PASS: gdb.cp/classes.exp: calling method for small class
> +FAIL: gdb.cp/classes.exp: calling method for small class
>
> git bisect pointed to this commit:
>
>    6ae8866180bf90e9ec76c2dd34c07fd826d11a83 is the first bad commit
>    commit 6ae8866180bf90e9ec76c2dd34c07fd826d11a83
>    Author: Luis Machado <lgustavo@codesourcery.com>
>    Date:   Wed Jun 17 16:50:57 2015 -0300
>
>        Fix problems with finishing a dummy function call on simulators.
>
> I don't have an offhand explanation for the regressions.
>
> This is just:
>
>   make check RUNTESTFLAGS="--target_board=native-gdbserver"
>
> on x86_64 Fedora 20.
>
> Thanks,
> Pedro Alves
>

I'll take a look at it. I suppose this will block the branching?

Then again, simply reverting this will still have bad results with some 
simulators.

  reply	other threads:[~2015-07-06 15:33 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 [this message]
2015-07-06 16:15                 ` Pedro Alves
2015-07-06 16:18                   ` Luis Machado
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=559A9FCE.5070908@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).