Author Topic: alternative GDB issue  (Read 125 times)

Online nenin

  • Almost regular
  • **
  • Posts: 221
alternative GDB issue
« on: Yesterday at 09:22:56 am »
I tried fresh gdb 14 from https://github.com//ssbssa
I configured it as "gdb14-64" (see attach 1 ) and assigned it to the toolchain (see attach 1), replacing native gdb form this toolchain, "nix64" (see attach 1).
However,  old "nix64" gdb is jumping out when I`m trying to debug (see attach 1). In default.conf all looks ok (attach 2), when I hacked "nix64" profile to use ssbssa gdb, it worked. Looks like somewhere in depth of the C::B old profile, "nix64", is not replaced with new one "gdb14-64".
"So it goes" (с)
Update: Problem was resolved according to https://forums.codeblocks.org/index.php/topic,22724.msg154381.html#msg154381 recommendation. Somehow "nix64" was assigned as "active debugger"  :-X
« Last Edit: Yesterday at 09:40:56 am by nenin »

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5929
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: alternative GDB issue
« Reply #1 on: Yesterday at 02:24:02 pm »
Grad to see you have solved your problem.

I use this GDB https://github.com//ssbssa for a long time. I think this GDB is better than the Msys2's GDB.

 :)
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.