User forums > General (but related to Code::Blocks)

[OT] unofficial MinGW GDB gdb with python released

<< < (32/35) > >>

ollydbg:
FYI: Hi all, I have release a new build, which is GDB 2016-01-30, see the updated first post  [OT] unofficial MinGW GDB gdb with python released for details.

MortenMacFly:

--- Quote from: ollydbg on January 30, 2016, 08:32:37 am ---FYI: Hi all, I have release a new build, which is GDB 2016-01-30, see the updated first post  [OT] unofficial MinGW GDB gdb with python released for details.

--- End quote ---
Great, thanks! I'll definitely give it a shot. (I have no other choice anyways... LOL.)

MortenMacFly:

--- Quote from: ollydbg on January 30, 2016, 08:32:37 am ---FYI: Hi all, I have release a new build, which is GDB 2016-01-30, see the updated first post  [OT] unofficial MinGW GDB gdb with python released for details.

--- End quote ---
Well too bad. Now this debugger also fails to debug wxWidgets applications on Windows. The error is:


--- Quote ---[debug]Error while reading shared library symbols for D:\Devel\CodeBlocks\src\devel\wxmsw28u_gcc_custom.dll:
[debug]D:\Devel\CodeBlocks\src\devel\wxmsw28u_gcc_custom.dll: error reading symbols
[debug]C:/crossdev/src/gdb-7.9.1/gdb/buildsym.c:1023: internal-error: prepare_for_building: Assertion `current_subfile == NULL' failed.
[debug]A problem internal to GDB has been detected,
[debug]further debugging may prove unreliable.
[debug]This is a bug, please report it.  For instructions, see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]This application has requested the Runtime to terminate it in an unusual way.
[debug]Please contact the application's support team for more information.

--- End quote ---

Does it work for you?

MortenMacFly:

--- Quote from: MortenMacFly on January 31, 2016, 05:52:32 pm ---Well too bad. Now this debugger also fails to debug wxWidgets applications on Windows. The error is:

--- End quote ---
Aaaarg! nevermind - I picked the wrong debugger.
@Teodor: Is it possible the clearly show the name of the debugger chosen before a debug session starts? This happens rather often to me... as I switch often...

However - I see another issue: "Import error: site" and that's it. :-/ Looks like the python stuff is broken for me...

oBFusCATed:
You want to see the name of the selected debugger configuration, right?
I think we print the path to the debugger already.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version