From: "Bahadir Balban" <bahadir.balban@gmail.com>
To: "Andreas Schwab" <schwab@suse.de>
Cc: gdb@sourceware.org
Subject: Re: breakpoint on non-function symbol
Date: Thu, 01 Feb 2007 11:26:00 -0000 [thread overview]
Message-ID: <7ac1e90c0702010326r74b32eabs2a28061d5e9ecede@mail.gmail.com> (raw)
In-Reply-To: <jetzy66t1s.fsf@sykes.suse.de>
On 2/1/07, Andreas Schwab <schwab@suse.de> wrote:
> "Bahadir Balban" <bahadir.balban@gmail.com> writes:
>
> > Is it possible to put a breakpoint on a symbol that is not a function?
>
> You can put a breakpoint at any address with the "break *ADDR" syntax.
>
> Andreas.
The problem is the address is not known in advance, so I had to rely
on the symbol. Anyway, I fixed it in assembler by:
.global symname;
.type symname, function;
.equ symname, addr
rather than including it in the linker script.
Thanks,
Bahadir
next prev parent reply other threads:[~2007-02-01 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 10:48 Bahadir Balban
2007-02-01 11:01 ` Andreas Schwab
2007-02-01 11:26 ` Bahadir Balban [this message]
2007-02-01 12:20 ` Daniel Jacobowitz
2007-02-01 23:21 ` Bahadir Balban
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=7ac1e90c0702010326r74b32eabs2a28061d5e9ecede@mail.gmail.com \
--to=bahadir.balban@gmail.com \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/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