On 01/21/2013 01:38 PM, Nick Overdijk wrote:
Ah of course. I didn't do that, I ran it myself manually on stage1. such as:
dsymutil stage1 valgrind stage1
That's because the call to valgrind is a bit hidden in some scripts that
are also used on linux. Should my way work?
I think it should;
On Jan 20, 2013, at 3:50 PM CST, Nick Overdijk wrote:
I have a nice stacktrace from some memory error in valgrind, and it fails to
print the source file + line number somewhere. Here's the trace:
==63113== Conditional jump or move depends on uninitialised value(s)
[…]
==63113==
Did you use --dsymutil=yes ?
J
On 01/20/2013 10:50 PM, Nick Overdijk wrote:
Howdy!
I have a nice stacktrace from some memory error in valgrind, and it fails to
print the source file + line number somewhere. Here's the trace:
==63113== Conditional jump or move depends on uninitialised
Ah of course. I didn't do that, I ran it myself manually on stage1. such as:
dsymutil stage1 valgrind stage1
That's because the call to valgrind is a bit hidden in some scripts that are
also used on linux. Should my way work?
On 2013-21-01, at 12:10:28 , Julian Seward wrote:
Did you use
