Displaying 3 results from an estimated 3 matches for "202961f81bbcf1a28139eae1d6fbf1ca".
2016 Dec 22
2
debug info "ref" parameter
...behavior when it sees an alloca.
Here's a simplified version, works on i386 windows and linux (most
likely 64bits too but i don't have that handy to test)
in gdb a break Test1; break Test2; run; step; locals (fine for Test1);
run; step; (broken for Test2)
https://gist.github.com/carlokok/202961f81bbcf1a28139eae1d6fbf1ca
--
Carlo Kok
RemObjects Software
2016 Dec 22
0
debug info "ref" parameter
...loca.
> Here's a simplified version, works on i386 windows and linux (most
> likely 64bits too but i don't have that handy to test)
>
> in gdb a break Test1; break Test2; run; step; locals (fine for Test1);
> run; step; (broken for Test2)
> https://gist.github.com/carlokok/202961f81bbcf1a28139eae1d6fbf1ca
>
> --
> Carlo Kok
> RemObjects Software
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161222/66485b57/attachment.html>
2016 Dec 22
0
debug info "ref" parameter
if you could simplify it down a bit, that might be helpful - not sure
there's a lot to be gained - I imagine it is just a quirk of how we handle
these things in the backend to make normal debug info work, but there might
be some things to be done to help.
On Wed, Dec 21, 2016 at 2:31 PM Carlo Kok <ck at remobjects.com> wrote:
>