User forums > Nightly builds

The 17 May 2012 build (7966) is out.

<< < (10/15) > >>

hooluupog:

--- Quote from: ollydbg on May 30, 2012, 07:12:34 am ---Hi, Hooluupog. I do not think so.

Codeblocks just serves as a front end of gdb, so the most situation is: gdb freeze cause codeblocks freeze.

I believe you can give use the log of both gdb (under Windows Shell) and the gdb log (under Codeblocks Debugger panel), then we can see whether you are true. :)

--- End quote ---
It just freezed,the debugger stopped working,and showed none gdb log output. Meanwhile cpu usage was keeping 50%(i3 quard Core cpu).You can see my screenshot.

[attachment deleted by admin]

oBFusCATed:
Don't use "set print elements 0" if you use it and you have large data structures it will be slow - end of discussion.

ollydbg:

--- Quote from: hooluupog on May 30, 2012, 08:42:08 am ---
--- Quote from: ollydbg on May 30, 2012, 07:12:34 am ---Hi, Hooluupog. I do not think so.

Codeblocks just serves as a front end of gdb, so the most situation is: gdb freeze cause codeblocks freeze.

I believe you can give use the log of both gdb (under Windows Shell) and the gdb log (under Codeblocks Debugger panel), then we can see whether you are true. :)

--- End quote ---
It just freezed,the debugger stopped working,and showed none gdb log output. Meanwhile cpu usage was keeping 50%(i3 quard Core cpu).You can see my screenshot.

--- End quote ---
OK, if you debug your program in GDB (Windows shell), the gdb should be freeze too.  :)

hooluupog:

--- Quote from: ollydbg on May 30, 2012, 09:07:52 am ---
--- Quote from: hooluupog on May 30, 2012, 08:42:08 am ---
--- Quote from: ollydbg on May 30, 2012, 07:12:34 am ---Hi, Hooluupog. I do not think so.

Codeblocks just serves as a front end of gdb, so the most situation is: gdb freeze cause codeblocks freeze.

I believe you can give use the log of both gdb (under Windows Shell) and the gdb log (under Codeblocks Debugger panel), then we can see whether you are true. :)

--- End quote ---
It just freezed,the debugger stopped working,and showed none gdb log output. Meanwhile cpu usage was keeping 50%(i3 quard Core cpu).You can see my screenshot.

--- End quote ---
OK, if you debug your program in GDB (Windows shell), the gdb should be freeze too.  :)

--- End quote ---
No,I have tried many times. In gdb command environment  it is very fast to print the elements but slow within codeblocks(nearly 5 mins or so to show the result,feels like it freezed).

oBFusCATed:
Yes, it is known issue...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version