From: Doug Evans <dje@transmeta.com>
To: mohanlal jangir <mohanlaljangir@hotmail.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: gdb shows source line multiple times before executing !!
Date: Thu, 24 Jul 2003 15:53:00 -0000 [thread overview]
Message-ID: <16160.204.590629.839217@casey.transmeta.com> (raw)
In-Reply-To: <20030724151959.GA7423@nevyn.them.org>
Daniel Jacobowitz writes:
> I recommend either not worrying about it, or
> looking at the assembly to understand what's going on.
It might also help to step through the assembly
instead of stepping line-by-line.
(gdb) display/i $pc
(gdb) stepi
[and keep repeating stepi, which will happen if at this point
you just keep hitting <return>]
prev parent reply other threads:[~2003-07-24 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 14:28 mohanlal jangir
2003-07-24 14:39 ` Nikola Kolev
2003-07-24 14:44 ` mohanlal jangir
2003-07-24 14:48 ` Daniel Jacobowitz
2003-07-24 14:56 ` mohanlal jangir
2003-07-24 15:17 ` Nikola Kolev
2003-07-24 15:20 ` Elena Zannoni
2003-07-24 15:20 ` Daniel Jacobowitz
2003-07-24 15:53 ` Doug Evans [this message]
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=16160.204.590629.839217@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mohanlaljangir@hotmail.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).