Author Topic: Splitting debugger in two - specific debugger and common GUI  (Read 300275 times)

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2193
Re: Splitting debugger in two - specific debugger and common GUI
« Reply #675 on: April 05, 2012, 10:47:22 pm »
Does this happen with the trunk's version?

Yes, pushing the abort button stops the pgm, but all build menus and toolbar buttons are grayed out.

So, I guess, it's a trunk problem.


Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9529
Re: Splitting debugger in two - specific debugger and common GUI
« Reply #676 on: April 12, 2012, 09:13:26 am »
...another one:
After the merge attaching to a process makes GDB crash. This used to work in the branch...?! Here is the debug log:

[debug]Command-line: C:\Devel\GCC46TDM\bin\gdb.exe -nx -fullname  -quiet
[debug]Working dir : D:\Code\Dummy

Starting debugger: C:\Devel\GCC46TDM\bin\gdb.exe -nx -fullname  -quiet
done

[debug]> set prompt >>>>>>cb_gdb:

Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Attaching to program with pid: 2928

[debug](gdb) >>>>>>cb_gdb:
[debug]> show version
[debug]GNU gdb (GDB) 7.3
[debug]Copyright (C) 2011 Free Software Foundation, Inc.
[debug]License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[debug]This is free software: you are free to change and redistribute it.
[debug]There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
[debug]and "show warranty" for details.
[debug]This GDB was configured as "mingw32".
[debug]For bug reporting instructions, please see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]>>>>>>cb_gdb:
[debug]> set confirm off

Debugger name and version: GNU gdb (GDB) 7.3

[debug]>>>>>>cb_gdb:
[debug]> set width 0
[debug]>>>>>>cb_gdb:
[debug]> set height 0
[debug]>>>>>>cb_gdb:
[debug]> set breakpoint pending on
[debug]>>>>>>cb_gdb:
[debug]> set print asm-demangle on
[debug]>>>>>>cb_gdb:
[debug]> set unwindonsignal on
[debug]>>>>>>cb_gdb:
[debug]> set print elements 0
[debug]>>>>>>cb_gdb:
[debug]> set debugevents on
[debug]>>>>>>cb_gdb:
[debug]> set disassembly-flavor att
[debug]>>>>>>cb_gdb:
[debug]> catch throw
[debug]No symbol table is loaded.  Use the "file" command.
[debug]Catchpoint 1 (throw)
[debug]>>>>>>cb_gdb:
[debug]> source C:\Devel\CodeBlocks\share\codeblocks/scripts/stl-views-1.0.3.gdb
[debug]>>>>>>cb_gdb:
[debug]> attach 2928
[debug]gdb: windows_init_thread_list

Child process PID: 2928

[debug][New Thread 2928.0xb74]
[debug][New Thread 2928.0xd98]
[debug][New Thread 2928.0xe2c]
[debug][New Thread 2928.0x35c]
[debug][New Thread 2928.0x104c]
[debug]=b74 code=LOAD_DLL_DEBUG_EVENT)

-> CRASH.

I'll try on the command lien to see what happens there... However, can somebody try to attach to a process, too?

EDIT: Crashes on the command line, too... WTF?!
« Last Edit: April 12, 2012, 09:16:42 am by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12239
    • Travis build status
Re: Splitting debugger in two - specific debugger and common GUI
« Reply #677 on: April 12, 2012, 09:21:34 am »
Your gdb is broken?

BTW: I'm locking this topic, because we've merged the code in trunk. If you have any questions/problems/suggestions/patches start a new topic in the appropriate sub-forum.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]