1

I was using gdb before Mojave update but now it is throwing errors:

(gdb) file a.out BFD: /Users/aliomerkeser/Desktop/a.out: unknown load command 0x32 BFD: /Users/aliomerkeser/Desktop/a.out: unknown load command 0x32 "/Users/aliomerkeser/Desktop/a.out": not in executable format: File format not recognized

Is that a compatibility issue or a configuration issue of mine?

I tried downgrading gdb and re-codesigning gdb.

keser
  • 2,472
  • 1
  • 12
  • 38

2 Answers2

1

Known bug with gdb on Mojave. Still not resolved. In the thread below there is a solution proposed which involves rebuilding gdb with some changes.

gdb 8.2 can't recognized executable file on macOS Mojave 10.14

Update: 8.2 has officially incorporated these changes, so doesnt have to be done manually.

Ravi
  • 36
  • 1
  • 6
  • While it's fine to link to an answer, your answer should be useful even if the link doesn't work. Maybe quote the relevant parts of the solution here. – merlyn Nov 02 '18 at 04:27
0

Valgrind still doesn't work on OSX Mojave but I am using heapusage an it is a pretty good alternative to valgrind

heapusage

keser
  • 2,472
  • 1
  • 12
  • 38