Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: ping huang <harderock@gmail.com>,
	shuchang zhou <shuchang.zhou@gmail.com>,
		gdb-patches@sourceware.org,
	Joel Brobecker <brobecker@adacore.com>,
		Michael Snyder <msnyder@vmware.com>,
	paawan oza <paawan1982@yahoo.com>,
		Tom Tromey <tromey@redhat.com>
Subject: Re: [RFC] Add support of software single step to process record
Date: Sun, 20 Jun 2010 07:29:00 -0000	[thread overview]
Message-ID: <AANLkTim8M55gdtPycCXIiCfWfA7X2_Ctoad6t7R14ZlI@mail.gmail.com> (raw)
In-Reply-To: <201006111455.36401.pedro@codesourcery.com>

On Fri, Jun 11, 2010 at 21:55, Pedro Alves <pedro@codesourcery.com> wrote:
> Hi Hui,
>
>> 3.  Ping got some gdb_assert in sometime.  And I am not close to his
>> board.  So I didn't know what happen.  So I add following:
>> @@ -1534,7 +1535,8 @@ a command like `return' or `jump' to con
>>        /* If STEP is set, it's a request to use hardware stepping
>>        facilities.  But in that case, we should never
>>        use singlestep breakpoint.  */
>> -      gdb_assert (!(singlestep_breakpoints_inserted_p && step));
>> +      gdb_assert (!(execution_direction == EXEC_FORWARD
>> +                    && singlestep_breakpoints_inserted_p && step));
>>
>> The lost one still need be test.
>
> I'm felling a bit dense, and I don't see what is that actually
> catching.  If going backwards, the assertion always ends up
> evaled as true, nomatter if sofware single-steps are inserted
> or not, or whether `step' is set.  Did you mean to assert
> that when going backwards, there shouldn't ever be software
> single-step breakpoints inserted?
>
> This patch is okay otherwise.  Thanks.
>
> --

Thanks Pedro.
I was also confused by this issue too.  I thought it will never happen
too.  But Ping said he got this issue.  And I didn't have the risc
board to test.  So I gived up and put this patch to him.

So I think this patch is not very hurry to checked in until some one
post a risc prec support patch.  At that time, I will make this issue
clear.

Best regards,
Hui


  reply	other threads:[~2010-06-20  7:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  8:21 Hui Zhu
2009-12-18 19:37 ` Michael Snyder
2009-12-20 13:48   ` Joel Brobecker
2009-12-23  6:38     ` Hui Zhu
2009-12-23  6:52       ` Joel Brobecker
2009-12-23  9:24         ` Hui Zhu
     [not found]           ` <8d62b6fe0912231751p1202294cw83430e8d53af0951@mail.gmail.com>
2009-12-24  1:54             ` Fwd: " shuchang zhou
2009-12-24 17:38           ` Pedro Alves
2010-01-04 14:23             ` Hui Zhu
2010-01-08 16:24               ` Pedro Alves
2010-05-25  5:14                 ` Hui Zhu
2010-05-27  6:51                   ` Hui Zhu
2010-06-11 13:55                     ` Pedro Alves
2010-06-20  7:29                       ` Hui Zhu [this message]
2010-06-22 10:13                         ` Pedro Alves
2010-07-19  7:58                           ` Hui Zhu
2009-12-22 18:23 ` Tom Tromey
2009-12-23  3:09   ` Hui Zhu

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=AANLkTim8M55gdtPycCXIiCfWfA7X2_Ctoad6t7R14ZlI@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=harderock@gmail.com \
    --cc=msnyder@vmware.com \
    --cc=paawan1982@yahoo.com \
    --cc=pedro@codesourcery.com \
    --cc=shuchang.zhou@gmail.com \
    --cc=tromey@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