[lldb-dev] [Bug 27416] missing global variables

2016-05-23 Thread via lldb-dev 
https://llvm.org/bugs/show_bug.cgi?id=27416

Marius Trandafir  changed:

   What|Removed |Added

   Assignee|lldb-dev@lists.llvm.org |marius.tranda...@live.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 27845] New: Name lookup on inline variables does not account for live ranges on Windows

2016-05-23 Thread via lldb-dev 
https://llvm.org/bugs/show_bug.cgi?id=27845

Bug ID: 27845
   Summary: Name lookup on inline variables does not account for
live ranges on Windows
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: ztur...@google.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

If you have this code:

#include 

void test1(int) __attribute__ ((always_inline));
void test2(int) __attribute__ ((always_inline));

void test2(int b) {
printf("test2(%d)\n", b);
}

void test1(int a) {
printf("test1(%d)\n",  a);
test2(a+1);
}

int main() {
test2(42);
test1(23);
}

And you put a breakpoint in test2, it will get hit first with the value b=42,
and then again with the value b=24.  If you're at the 2nd hit of the breakpoint
and you try to print the value of b, it says the name is ambiguous (presumably
because it can't decide between the first and the second b).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] How to link lldb on i386

2016-05-23 Thread Greg Clayton via lldb-dev 
Don't generate debug info would be one that comes to mind. The other is to 
cross build for i386 on a 64 bit machine.

Greg

> On May 22, 2016, at 3:36 AM, Sylvestre Ledru via lldb-dev 
>  wrote:
> 
> Hello,
> 
> Lately, I haven't been able to link lldb because it uses too much memory:
> 
> /usr/bin/ld: final link failed: Memory exhausted
> 
> As reported here:
> 
> https://llvm.org/bugs/show_bug.cgi?id=27237
> 
> 
> (yes, I use shared libraries)
> 
> Any workaround?
> 
> Thanks,
> Sylvestre
> PS: please cc me !
> 
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] How to link lldb on i386

2016-05-23 Thread Zachary Turner via lldb-dev 
cross building on a 64-bit machine using a 64-bit toolchain is what we have
to do on Windows.

On Mon, May 23, 2016 at 2:21 PM Greg Clayton via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> Don't generate debug info would be one that comes to mind. The other is to
> cross build for i386 on a 64 bit machine.
>
> Greg
>
> > On May 22, 2016, at 3:36 AM, Sylvestre Ledru via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> >
> > Hello,
> >
> > Lately, I haven't been able to link lldb because it uses too much memory:
> >
> > /usr/bin/ld: final link failed: Memory exhausted
> >
> > As reported here:
> >
> > https://llvm.org/bugs/show_bug.cgi?id=27237
> >
> >
> > (yes, I use shared libraries)
> >
> > Any workaround?
> >
> > Thanks,
> > Sylvestre
> > PS: please cc me !
> >
> > ___
> > lldb-dev mailing list
> > lldb-dev@lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev