Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

C::B svn6346 hang report always on closing

<< < (3/3)

Jenna:

--- Quote from: ollydbg on July 03, 2010, 04:18:37 am ---
--- Quote from: oBFusCATed on July 02, 2010, 08:05:15 pm ---Can you try to build codeblocks with --enable-debug?
Then run gdb codeblocks and when cb crashes, execute the bt command in gdb.

There is a possibility for a crash if a plugin (or someone else I don't remember the details) writes something to the log during the shutdown of CB.

--- End quote ---

--enable-debug  is a option to let Codeblocks open a debug log panel.

In windows, CB is always build with debug information, so, you can debug CB under CB, if the debugee CB crashes, the debugger CB can get the call stack information

--- End quote ---

That's not correct !!

--enable-debug is an option of the configure-script linux !
The option you mentioned is --debug-log or -d on commandline and has nothing to do with it.
On linux I suggest not to use it, because C::B's internal debug-output is written to the console if the debug-log is not used. If it is used the information is lost after a crash. You have to start C::B from console to see it of course.

@Deschamps:

if you rebuild C::B, you can turn on additional debug-logging in OnInit() in app.cpp, change the parameter of wxLog::EnableLogging(false); to true before the build and you get some warnings that can be ignored and possibly (hopefully) some more information.

ollydbg:

--- Quote from: jens on July 03, 2010, 09:27:35 am ---
--- Quote from: ollydbg on July 03, 2010, 04:18:37 am ---
--- Quote from: oBFusCATed on July 02, 2010, 08:05:15 pm ---Can you try to build codeblocks with --enable-debug?
Then run gdb codeblocks and when cb crashes, execute the bt command in gdb.

There is a possibility for a crash if a plugin (or someone else I don't remember the details) writes something to the log during the shutdown of CB.

--- End quote ---

--enable-debug  is a option to let Codeblocks open a debug log panel.

In windows, CB is always build with debug information, so, you can debug CB under CB, if the debugee CB crashes, the debugger CB can get the call stack information

--- End quote ---

That's not correct !!

--enable-debug is an option of the configure-script linux !
The option you mentioned is --debug-log or -d on commandline and has nothing to do with it.
On linux I suggest not to use it, because C::B's internal debug-output is written to the console if the debug-log is not used. If it is used the information is lost after a crash. You have to start C::B from console to see it of course.

--- End quote ---

I'm sorry, that was my big Mistake.  :(

Deschamps:
Hello again.

There are some changes in regards to my last post. The situation has maintained at least until revision 6400, but I've recently compiled svn revision 6425 (with wxSmith and related plugins -wxSmithAUI and wxsmithcontribitems- disabled due to the different version for the C::B SDK), and all is going fine. No more hang reports from BugBuddy each time I was closing Code::Blocks.

Good news at last.

But, I don't know if this is because wxSmith is disabled (this will be easily checked), or some change has solved this problem between revs 6400 and 6425, or because this was caused by my environment, who has also been updated (kernel 2.6.34, gcc 4.5.0 20100610 and GNOME 2.30-2).

The fact is that C::B is not throwing hang reports anymore :)

Kindest regards.

Navigation

[0] Message Index

[*] Previous page