Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Xingxing Pan <forandom@gmail.com>
To: gdb <gdb@sourceware.org>
Subject: 'maybe_software_singlestep' inserts breakpoints when record replay
Date: Tue, 09 Nov 2010 15:40:00 -0000	[thread overview]
Message-ID: <AANLkTi=fkBydf9Au2u3kHg4U2x0jt3H8jUqyKwBYhvK_@mail.gmail.com> (raw)

Hi guys,

I'm porting the process record to an arch which only supports software
singlestep.

And I found that in the function 'resume', the function
'maybe_software_singlestep' inserts a software singlestep breakpoint
although the inferior is in record replay, and return a zero value to
the variable 'step'. When I use the command 'reverse-stepi',  gdb
cannot stop after reversely executing one instruction .

I try to prevent 'maybe_software_singlestep' from inserting a software
singlestep breakpoint when 'RECORD_IS_REPLAY' is asserted. Then the
error is disappeared.

I cannot figure out why we need to insert a software singlestep
breakpoint when gdb is travelling along the record_list back and
forth. Is this a bug?

Thanks,
Pan Xingxing


             reply	other threads:[~2010-11-09 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 15:40 Xingxing Pan [this message]
2010-11-09 22:44 ` 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='AANLkTi=fkBydf9Au2u3kHg4U2x0jt3H8jUqyKwBYhvK_@mail.gmail.com' \
    --to=forandom@gmail.com \
    --cc=gdb@sourceware.org \
    /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