Opened 3 years ago
Last modified 16 months ago
#6332 new defect
Valgrind segfaults on macOS
Reported by: | Stan | Owned by: | |
---|---|---|---|
Priority: | Should Have | Milestone: | Backlog |
Component: | Core engine | Keywords: | |
Cc: | Patch: |
Description
When running valgrind on macOS with the following command, the game segfaults
valgrind --leak-check=yes /Users/picus/0ad/binaries/system/pyrogenesis
Doing lldb
picus@Picus 0ad % lldb /usr/local/Cellar/valgrind/HEAD-3568e0b/bin/valgrind /Users/picus/0ad/binaries/system/pyrogenesis (lldb) target create "/usr/local/Cellar/valgrind/HEAD-3568e0b/bin/valgrind" Current executable set to '/usr/local/Cellar/valgrind/HEAD-3568e0b/bin/valgrind' (x86_64). (lldb) settings set -- target.run-args "/Users/picus/0ad/binaries/system/pyrogenesis" (lldb) run --leak-check=yes Process 69353 launched: '/usr/local/Cellar/valgrind/HEAD-3568e0b/bin/valgrind' (x86_64) Process 69353 stopped * thread #2, stop reason = exec frame #0: 0x00000002580f17b0 -> 0x2580f17b0: movabsq $0x2582a8000, %rdi ; imm = 0x2582A8000 0x2580f17ba: addq $0x2000, %rdi ; imm = 0x2000 0x2580f17c1: addq $0x100000, %rdi ; imm = 0x100000 0x2580f17c8: andq $-0x10, %rdi Target 0: (No executable module.) stopped. (lldb)
Full Output
https://termbin.com/r0fv
Note:
See TracTickets
for help on using tickets.
Unlikely to get done for A26