Matthew Gardiner wrote:
Therefore if one of our users wants to disassemble from the code bus,
they'd say
(lldb) di -s 0x804004f0
Actually a colleague suggested that rather than adding an offset/setting a bit, we could
augment the address with a decorator, e.g. "c"
(lldb) di -s 0x4
Greg:
Thanks for all your code suggestions. I can't comment on them just now
as I'm still single-stepping the existing code and trying to think it
all through.
lldb-dev:
I can't help but think though that I'm going have problems in getting
the lldb disassembler to work against a traditional
> On Jun 2, 2014, at 4:06 AM, Matthew Gardiner wrote:
>
> Greg Clayton wrote:
>> Addresses in LLDB are represented by
>>
>> class lldb_private::Address {
>> lldb::SectionWP m_section_wp;///< The section for the address, can
>> be NULL.
>> std::atomic m_offset; ///< Offset into sect
Greg Clayton wrote:
Addresses in LLDB are represented by
class lldb_private::Address {
lldb::SectionWP m_section_wp; ///< The section for the address, can
be NULL.
std::atomic m_offset; ///< Offset into section if \a
m_section_wp is valid...
}
The section class:
class lldb_pri
> On May 29, 2014, at 11:45 PM, Matthew Gardiner wrote:
>
> Hi folks,
>
> I have been researching using lldb and a custom gdbserver stub to debug some
> of our processors. I have already played with ArchSpec.h/.cpp/Elf.h to add a
> processor definition, and since our tools output DWARF inform
Abid, Hafiz wrote:
So is the "add an offset" technique still the best way forward to solve this
problem? How about adding a new request (along with a query request to
interrogate the stub for support) for code reads - is this an option?
(If so, I'd be happy to do the work...)
If you do this, the
ge-
> From: lldb-dev-boun...@cs.uiuc.edu [mailto:lldb-dev-boun...@cs.uiuc.edu]
> On Behalf Of Matthew Gardiner
> Sent: 30 May 2014 07:45
> To: lldb-dev@cs.uiuc.edu
> Subject: [lldb-dev] Advice on debugging DSP and Harvard architectures
>
> Hi folks,
>
> I have bee
Hi folks,
I have been researching using lldb and a custom gdbserver stub to debug
some of our processors. I have already played with ArchSpec.h/.cpp/Elf.h
to add a processor definition, and since our tools output DWARF
information, have already managed to use lldb to dump line tables.
On the
