From: Joel Brobecker <brobecker@adacore.com>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Symbols/blocks questions
Date: Sat, 19 Sep 2009 16:34:00 -0000 [thread overview]
Message-ID: <20090919163344.GL7961@adacore.com> (raw)
In-Reply-To: <200909191552.02677.ghost@cs.msu.su>
> 1. Given 'struct block *b', is it true that
>
> block_for_pc (b.startaddr) == b
My guess is that this is NOT true. Two blocks could have the same
start address if one block is nested inside the other...
> 2. Uness I am mistaken, in case of lines inside templates,
> inline functions, and constructors, decode_line_1 returns
> just one sal. (And breakpoint.c explicitly expands thsoe in
> expand_line_sal). In what cases will decode_line_1 actually
> return multiple sals? For overloaded functions? Anything else?
> Would it be sensible, eventually, to make decode_line_1
> return all locations corresponding to file:line?
>
> 3. The code below, from Apple GDB, first calls decode_line_1
> and then checks, for each sal, if the line passed to decode_line_1
> is less then sal.line. How could this happen at all? I though that
> if I ask decode_line_1 for line 10, then either it returns sals
> for line 10, or it returns no sal at all.
Jerome Guitton had a serious look at how things are done when
decoding breakpoint locations, mostly because we wanted Ada and C++
to use the same code for multiple-location breakpoints. I'll ask him
to see there is any useful piece of information that might help answer
these questions.
--
Joel
next prev parent reply other threads:[~2009-09-19 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 11:52 Vladimir Prus
2009-09-19 14:34 ` Matt Rice
2009-09-19 16:34 ` Joel Brobecker [this message]
2009-09-19 16:41 ` Vladimir Prus
2009-09-19 17:02 ` Joel Brobecker
2009-09-19 18:35 ` Vladimir Prus
2009-09-20 15:52 ` Joel Brobecker
2009-09-20 20:30 ` Daniel Jacobowitz
2009-09-22 9:47 ` Jerome Guitton
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=20090919163344.GL7961@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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