search

sowson / valgrind

Experimental Version of Valgrind for macOS 10.14.6 Mojave and 10.15.4 Catalina (10.15.x NOT WORKING)
git://sourceware.org/git/valgrind.git
GNU General Public License v2.0
133 stars 17 forks source link

==16093== Memcheck, a memory error detector #4

Open kirilltitov1 opened 4 years ago

kirilltitov1 commented 4 years ago
image image

I have a problem after updating mojave on catalina 10.15.2 valgrind does not run a memory check. although it was obvious.

sowson commented 4 years ago

To be honest I rollback thanks to the time machine to the macOS High Sierra and I can share that it does not work either...

--2337-- run: /usr/bin/dsymutil "/Users/piotrsowa/Projects/github/darknet/cmake-build-debug/darknet" --2337-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option --2337-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times) --2337-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times) ==2337== valgrind: Unrecognised instruction at address 0x102576b7b. ==2337== Your program just tried to execute an instruction that Valgrind ==2337== did not recognise. There are two possible reasons for this. ==2337== 1. Your program has a bug and erroneously jumped to a non-code ==2337== location. If you are running Memcheck and you just saw a ==2337== warning about a bad jump, it's probably your program's fault. ==2337== 2. The instruction is legitimate but Valgrind doesn't handle it, ==2337== i.e. it's Valgrind's fault. If you think this is the case or ==2337== you are not sure, please let us know and we'll try to fix it. ==2337== Either way, Valgrind will now raise a SIGILL signal which will ==2337== probably kill your program.