https://bugs.kde.org/show_bug.cgi?id=383723
--- Comment #5 from John Reiser <jrei...@bitwagon.com> --- The crash looks very similar to the 'ud2' diagnosed in the original Description. In particular, the offset 0x....b50 is the same. This probably indicates that valgrind has more-or-less completely missed some aspect of what MacOS is doing. We need advice from an expert. <joke> So, spend two weeks at the bar/pub/tavern/restaurants in Cupertino and Sunnyvale. Buy a beer for the next 10 people who enter. Chat them up. </joke> Apply dtruss and/or dtrace to the original program without valgrind, and to valgrind when running the program. Correlate the system calls between the two runs; try to understand the difference. [Also investigate "valgrind --trace-syscalls=yes ..." as an additional or alternate source of information.] That's quite tedious, but logically should work. Also, contrast with running on Linux (which uses 'strace'). The Qt implementation might be similar enough to provide a clue. -- You are receiving this mail because: You are watching all bug changes.
