On Mar 1, 2016, at 11:45 AM, Zachary Turner wrote:
>
> Alright I think i get it. Basically terminal entry means "everything from
> this address onwards is not part of any function"
Yes
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llv
Alright I think i get it. Basically terminal entry means "everything from
this address onwards is not part of any function"
On Tue, Mar 1, 2016 at 11:36 AM Greg Clayton wrote:
>
> > On Mar 1, 2016, at 11:30 AM, Zachary Turner wrote:
> >
> > We do know the last line of a function. In the review i
> On Mar 1, 2016, at 11:30 AM, Zachary Turner wrote:
>
> We do know the last line of a function. In the review i posted, you can see
> the condition where i set is_epilogue to true. That is the last line of a
> function corresponding to the } (although the function may contain additional
> by
We do know the last line of a function. In the review i posted, you can see
the condition where i set is_epilogue to true. That is the last line of a
function corresponding to the } (although the function may contain
additional bytes, since that only refers to the first byte of the epilogue.
But I
> On Feb 29, 2016, at 5:51 PM, Zachary Turner wrote:
>
>
>
> On Mon, Feb 29, 2016 at 5:49 PM Zachary Turner wrote:
> Those are addresses. Here's the situation I was encountering this on:
>
> // foo.h
> #include "bar.h"
> inline int f(int n)
> {
> return g(n) + 1;
> }
>
> // bar.h
> inl
On Mon, Feb 29, 2016 at 5:49 PM Zachary Turner wrote:
> Those are addresses. Here's the situation I was encountering this on:
>
> // foo.h
> #include "bar.h"
> inline int f(int n)
> {
> return g(n) + 1;
> }
>
> // bar.h
> inline int g(int n)
> {
> return n+1;
> }
>
> // foo.cpp
> #includ
Those are addresses. Here's the situation I was encountering this on:
// foo.h
#include "bar.h"
inline int f(int n)
{
return g(n) + 1;
}
// bar.h
inline int g(int n)
{
return n+1;
}
// foo.cpp
#include "foo.h"
int main(int argc, char** argv)
{
return f(argc);
}
PDB gives me back li
> On Feb 29, 2016, at 5:09 PM, Zachary Turner wrote:
>
> Suppose you've got two line sequences.
>
> First sequence:
> 4198512
> 4198544
> 4198547
> 4198562
>
> Second sequence:
> 4198528
> 4198531
> 4198537
> 4198552
>
> These two line sequences overlap, and will not be inserted correctly i
Suppose you've got two line sequences.
First sequence:
4198512
4198544
4198547
4198562
Second sequence:
4198528
4198531
4198537
4198552
These two line sequences overlap, and will not be inserted correctly into a
LineTable. This sounds like a bug to me, because as far as I can tell
there is noth
On Thu, Feb 11, 2016 at 5:35 PM Greg Clayton wrote:
>
> > 5. ParseCompileUnitLineTable. On the LineTable class you can add "line
> sequences" or individual entries. What's the difference here? Is there
> any disadvantage to adding every single line entry in the line table using
> the InsertLin
On Fri, Feb 12, 2016 at 9:41 AM Greg Clayton wrote:
>
> > On Feb 11, 2016, at 6:56 PM, Zachary Turner wrote:
> >
> >
> >
> > On Thu, Feb 11, 2016 at 5:35 PM Greg Clayton wrote:
> >
> > > On Feb 11, 2016, at 3:41 PM, Zachary Turner via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> > >
> > > Hi,
> On Feb 11, 2016, at 6:56 PM, Zachary Turner wrote:
>
>
>
> On Thu, Feb 11, 2016 at 5:35 PM Greg Clayton wrote:
>
> > On Feb 11, 2016, at 3:41 PM, Zachary Turner via lldb-dev
> > wrote:
> >
> > Hi,
> >
> > I want to make a new symbol provider to teach LLDB to understand microsoft
> > PDB
On Thu, Feb 11, 2016 at 5:35 PM Greg Clayton wrote:
>
> > On Feb 11, 2016, at 3:41 PM, Zachary Turner via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> >
> > Hi,
> >
> > I want to make a new symbol provider to teach LLDB to understand
> microsoft PDB files. I've been looking over the various sy
> On Feb 11, 2016, at 3:41 PM, Zachary Turner via lldb-dev
> wrote:
>
> Hi,
>
> I want to make a new symbol provider to teach LLDB to understand microsoft
> PDB files. I've been looking over the various symbol APIs, and I have a few
> questions.
>
> 1. Under what circumstances do I need
Hi,
I want to make a new symbol provider to teach LLDB to understand microsoft
PDB files. I've been looking over the various symbol APIs, and I have a
few questions.
1. Under what circumstances do I need a custom SymbolVendor? The way pdb
works is that generally there is 1 file that contains al
15 matches
Mail list logo
