Recent

« previous next »
Pages: [1]

Author Topic: GDB signed but still cannot run debugger  (Read 6458 times)

bdoan@oro.net

  • Newbie
  • Posts: 3
GDB signed but still cannot run debugger
« on: January 18, 2015, 06:11:40 pm »
I have installed Lazarus 1.2.6 on a Mac Mini (OSX 10.10.1 Yosemite) and GDB debugger 7.8.1

Finally able to CodeSign GDB but debugger does not run.

",msg="Unable to find Mach task port for process-id 678: (os/kern) failure (0x5).\n (please check gdb is codesigned - see taskgated(8))""

Any clues on how to fix?
Logged

Jonas Maebe

  • Hero Member
  • *****
  • Posts: 1071
Re: GDB signed but still cannot run debugger
« Reply #1 on: January 18, 2015, 10:32:43 pm »
It means that gdb was not codesigned appropriately. Make sure to follow all instructions at http://www.sourceware.org/gdb/wiki/BuildingOnDarwin
Logged

bdoan@oro.net

  • Newbie
  • Posts: 3
Re: GDB signed but still cannot run debugger
« Reply #2 on: January 19, 2015, 12:36:49 am »
GDB reports that it is already code signed.

Can I "unsign" it and try again?

Or should I just modify the key?
Logged

Jonas Maebe

  • Hero Member
  • *****
  • Posts: 1071
Re: GDB signed but still cannot run debugger
« Reply #3 on: January 19, 2015, 02:45:07 pm »
With the -f parameter of codesign, you can replace an existing signature with a new one.
Logged

bdoan@oro.net

  • Newbie
  • Posts: 3
Re: GDB signed but still cannot run debugger
« Reply #4 on: January 19, 2015, 10:38:33 pm »
-f instead of -s ?

it returns a list of menu items (no -f included)

Logged

Jonas Maebe

  • Hero Member
  • *****
  • Posts: 1071
Re: GDB signed but still cannot run debugger
« Reply #5 on: January 19, 2015, 11:11:21 pm »
-f in addition to -s (it means "force"). See "man codesign" for more information.
Logged
Pages: [1]
« previous next »
 

TinyPortal © 2005-2018