Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jason Luo <jasonl@turbolinux.com.cn>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: What make the directive run twice?
Date: Fri, 04 Jun 2004 02:34:00 -0000	[thread overview]
Message-ID: <40BFDEC8.3070602@turbolinux.com.cn> (raw)
In-Reply-To: <20040603204433.GA22683@nevyn.them.org>

> It wasn't run twice; it appears in the step output twice.  This is
> common when debugging optimized code; part of the function call occurs
> before the previous line and part after.

I disassemble the call function init_device_map,and the function 
check_device,I didn't find that you says.

init_device_map call check_deivce,then the control jump to the function 
check_device,then process continue.The process flow is correct  like the 
c source file's.

I guess you say is the binary code was optimized,isn't it? Counld you 
reference to me about the point?Thanks!


Best Regards
Jason



  reply	other threads:[~2004-06-04  2:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  7:10 Jason Luo
2004-06-03 20:44 ` Daniel Jacobowitz
2004-06-04  2:34   ` Jason Luo [this message]
2004-06-04 12:11     ` Eli Zaretskii

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=40BFDEC8.3070602@turbolinux.com.cn \
    --to=jasonl@turbolinux.com.cn \
    --cc=drow@false.org \
    --cc=gdb@sources.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