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

C::B svn6346 hang report always on closing

<< < (2/3) > >>

Jenna:

--- Quote from: gd_on on June 12, 2010, 07:58:21 pm ---Hi again,
I tried to to that, to have a really fresh rebuild. But I obtain always the same messages on some compilations, but I think less than before (for example still in Code Snippets).
May be a new problem because I use now tdm gcc 4.5. But ???
As I said, not a great problem, because C::B is finally correctly compiled (I think  :?).

gd_on


--- End quote ---
These messgages come, because pch's can only be used with the same defines as they have been built. It should have nothing to do with gcc 4.5.

Deschamps:
Hi again.

Well, the situation continued after trying a cleaned rebuild with newer revisions, so I uninstalled and erased all, building C::B from scratch, from svn r6379 sources just checked out. And still I'm receiving that hang report on closing the IDE.

So I'll try to compile in a while an old sources revision (I think that rev6336 and older were closing fine) so I could assume that it's not a C::B behavior, but something in my box causing this issue.

Regards.

Deschamps:
:( Ok. I've just downloaded from the repository and compiled C::B rev.6336 sources, with the hope that it would show the same hang warning I've been receiving these weeks each time I was exiting the IDE, thinking that this could let me confirm that there is something wrong with my Archlinux distribution... But, nope! C::B svn r6336 is closing without problems nor hang reports.

So that, now I'm sure that there is something that I've not identified between rev.6336 and rev.6346 (and maintained in later revisions) that makes BugBuddy to throw a hang report each time C::B is closed, at least for my environtment.

Regards.

oBFusCATed:
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.

ollydbg:

--- 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

Navigation

[0] Message Index

[#] Next page

[*] Previous page