Reporting a FREEZE bug

[Death Knight]

Hi, My codeblocks (svn) has a bug. It's locking... Than there is no debug output. How can I apply manual debug report? I don't know GDB well. Thank you.

[Der Meister]

You should be able to get a backtrace if you follow the following steps:

• Run "gdb codeblocks"
• Enter "r" in the gdb prompt. Code::Blocks should start.
• Do whatever you did to make Code::Blocks freeze.
• Switch back to the console where gdb is running and hit "Ctrl+C". You should see something like "Program received signal SIGINT, Interrupt."
• Enter "bt" in the gdb command prompt. It should print you a backtrace.
• Post the (full!) backtrace here in this thread.

(Note: This works on Linux, I don't know if it works on Windows, too.)

[Death Knight]

Hi,
Thanks for code lines, but when Codeblocks freezed, my entire  desktop is freezes.
(it's triggered by Codeblocks, specialy when I select text and move somewhere... )

I can kill codeblocks with CTRL+ALT+F1 (tty1)

You advicing me for running codeblocks with GDB...
I think this not work because GDB has to be started from tty1, isn't it?

[Death Knight]

DISPLAY=:0.0 solved my problem, Now I started program, when it freezes I will post debug output here.
I wonder  how can I copy/paste tty window? :
might be running with
gdb codeblocks > debug.txt helps.
Thanks master

[Death Knight]

I have problem with GDB
Program locks most of time when running inside of GDB.
(I compiled this C::B with fress SVN, with also  --enable-debug flag)


death@eua:~> gdb codeblocks
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-suse-linux"...Using host libthread_db library "/lib64/libthread_db.so.1".

(gdb) r
Starting program: /usr/local/bin/codeblocks
[Thread debugging using libthread_db enabled]
[New Thread 47685905327792 (LWP 1680)]
[New Thread 1082132800 (LWP 1683)]
[New Thread 1090525504 (LWP 1684)]
[New Thread 1098918208 (LWP 1685)]
[New Thread 1107310912 (LWP 1686)]
[New Thread 1115703616 (LWP 1687)]
[New Thread 1124096320 (LWP 1689)]
[New Thread 1132489024 (LWP 1692)]
[Thread 1132489024 (zombie) exited]
thread_db_get_info: cannot get thread info: generic error
(gdb) bt
#0  0x0000000000000000 in ?? ()
Cannot access memory at address 0x0
(gdb)

[Der Meister]

I wonder  how can I copy/paste tty window? :
might be running with
gdb codeblocks > debug.txt helps.

This way you won't see the output of gdb but this command should help:

Code

gdb codeblocks | tee debug.txt

Now the output will be printed to stdout *and* debug.txt.

thread_db_get_info: cannot get thread info: generic error

Too bad. Had this message sometimes, too. Did you try to continue with debugging (entering "c" as command)? I think this helped me from time to time.

[kai]

I assume that is the bug which freezes code::blocks in a drag state of a drag and drop operation. that was a wxwidgets bug which has recently been fixed in wxwidgets2.8 cvs. so for now just be careful when you click on a tab.

[Death Knight]

Hi,

I don't saw this message, next time, I will be try with "|tee" this...
But I captured freeze time with
>gdb --pid=xxxx > debug.txt
command.
I don't think it will be helpfull. But I needed to send it...

I attached this file.

thread_db_get_info: cannot get thread info: generic error

Too bad. Had this message sometimes, too. Did you try to continue with debugging (entering "c" as command)? I think this helped me from time to time.

I am rookie with gdb, I will use 'c' option next time

For Kai:
It might be that bug. it happens commonly drag n drop "tabs" and "text selections".

[attachment deleted by admin]