From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: kdsfinger@gmail.com, gdb@sourceware.org
Subject: Re: gdb breakpoint problem
Date: Mon, 11 Jun 2007 20:21:00 -0000 [thread overview]
Message-ID: <u8xaqjl89.fsf@gnu.org> (raw)
In-Reply-To: <m3vedus8aj.fsf@codesourcery.com> (message from Jim Blandy on Mon, 11 Jun 2007 10:36:04 -0700)
> Cc: gdb@sourceware.org
> From: Jim Blandy <jimb@codesourcery.com>
> Date: Mon, 11 Jun 2007 10:36:04 -0700
>
> What's probably going on is that there is no machine code generated
> for lines 24 and 25. They're just declarations. The first actual
> machine instruction in main is for line 26, so the 'addresses' of lines
> 24, 25, and 26 are probably all the same.
>
> You can try setting three breakpoints on lines 24, 25, and 26, and
> then comparing the addresses printed for each to see if this is the
> case.
Or just use the "info line" command to tell you directly what
addresses does each line compile to.
next prev parent reply other threads:[~2007-06-11 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 17:00 kdsfinger
2007-06-11 17:22 ` Daniel Jacobowitz
2007-06-11 17:36 ` Jim Blandy
2007-06-11 20:21 ` Eli Zaretskii [this message]
2007-06-12 3:33 ` kdsfinger
2007-06-12 11:19 ` Daniel Jacobowitz
2007-06-12 11:29 ` Dave Korn
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=u8xaqjl89.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=kdsfinger@gmail.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