Thanks Pat.Here's the output of otool -v -t checkIs this what is required?Do
let me know if I need to disassemble in some other way.
---check:(__TEXT,__text)
sectionstart:00010c78 pushq $0x010c7a movq
Thanks John!I will probably upgrade my XCode soon.
Because my effort failed to reproduce the bad behavior that you see,
then the response to a bug report may well be upgrade your XCode/Developer.
Unless there is a good reason for insisting on fixing the interaction of
valgrind with old
Hmm...I think there's a difference in the environment.
For me:About This Mac More Info... System Report... Software Developer:
Version: 3.2 (10M2518) Location:/Developer Applications:
Xcode: 3.2.6 (1761) Interface Builder:3.2.6 (851) Instruments:
2.7
Thanks John and Pat.
So what I understand is I can ignore the warning in this case.But, I still get
the warning even with --partial-loads-ok=yes. Why so?
- Tan
Below is the output with
Thanks John!
The libc shared library does not seem to mention any version number. I'm on
MacOs 10.6.8 on Intel. How do I get the version of libc?Here's what I get from
valgrind -v:
-==57528== Memcheck, a
memory error detector==57528==
