> On Feb 29, 2016, at 11:02 PM, Jeffrey Tan wrote:
>
> My assumption is that different sections of the binary will be mapped
> continuously in memory; and the first section(which should be a header
> section for the binary) will stands for the base address of the whole module.
> Is this assum
My assumption is that different sections of the binary will be mapped
continuously in memory; and the first section(which should be a header
section for the binary) will stands for the base address of the whole
module.
Is this assumption not true for all platforms? Basically, I would like to
show t
As Jim said there really isn't just one address per module. You will want to
display the address of each of the sections for a module under that module. So
something like:
a.out
|- .text @ 0x1
|- .data @ 0x2
\- .bss @ 0x3
> On Feb 29, 2016, at 2:02 PM, Jeffrey Tan wrote:
>
There isn’t necessarily A load address for an SBModule. After all, the
different segments could load with different offsets. We usually list the
offset of the __TEXT__ address as the load address - for instance in “image
list", since if you are only interested in symbolication, that’s what you
Btw: I did not find an API to retrieve the load address of the SBModule?
This seems to be weird to me, did I miss anything?
On Mon, Feb 29, 2016 at 1:34 PM, Jeffrey Tan
wrote:
> I see why I did not find them in the first place. These two APIs are not
> listed in the official doc:
> http://lldb.
Greg, missed your reply. Yeah, the problem is that I only looked at the
python API(which is what I am using) doc which does not contain these APIs.
On Mon, Feb 29, 2016 at 12:43 PM, Greg Clayton wrote:
> In general where you see the event bits defined like SBTarget.h for your
> case, the class t
I see why I did not find them in the first place. These two APIs are not
listed in the official doc:
http://lldb.llvm.org/python_reference/index.html
Someone might want to add it.
Thanks
Jeffrey
On Mon, Feb 29, 2016 at 11:59 AM, Jeffrey Tan
wrote:
> This is very useful, thanks for the info!
>
In general where you see the event bits defined like SBTarget.h for your case,
the class that contains the event bit definitions:
class SBTarget
{
public:
//--
// Broadcaster bits.
//--
This is very useful, thanks for the info!
On Mon, Feb 29, 2016 at 10:36 AM, Jim Ingham wrote:
>
> On Feb 27, 2016, at 8:34 PM, Jeffrey Tan via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> Hi,
>
> I am trying to listen for module/symbol load/unload events and display
> them in output UI so th
> On Feb 27, 2016, at 8:34 PM, Jeffrey Tan via lldb-dev
> wrote:
>
> Hi,
>
> I am trying to listen for module/symbol load/unload events and display them
> in output UI so that debugger users can have a basic clue what is debugger
> busy doing while launching a big executable linking many sha
Hi,
I am trying to listen for module/symbol load/unload events and display them
in output UI so that debugger users can have a basic clue what is debugger
busy doing while launching a big executable linking many shared libraries.
Questions:
1. I did not find an API to get current load/unload modu
11 matches
Mail list logo
