User forums > Using Code::Blocks

What to do with debug reports

(1/2) > >>

littlegene:
Hi.
I was using C::B from one quite stable revision of 8xxx for a year or more.

Now I've just built 13.12-rc2 from source (on Linux), installed it and launched.
After nice-looking splash screen and compilers' settings upgrades agreement, I've got something like debug report with writing the message to /tmp/codeblocks_dbgrpt-xxxxx-xxxxxxxxxxxxxxx.
C::B exits now each time I am launching it.

Whom to inform about that debug report and where to post its contents?

(I think (but not sure of course) this error has to do with interraction between OLD wxwidgets-2.8 with NEW C::B revisions. The attempt to launch new builds of C::B in Windows force memory violation with something looking like 0x500000.... error)

MortenMacFly:

--- Quote from: littlegene on December 27, 2013, 08:21:39 am ---Whom to inform about that debug report and where to post its contents?

--- End quote ---
Well first you can try to delete your config under ~/.codeblocks usually named default.conf. (Make a backup before!)...

And post the contents here - thats fine.

littlegene:
I've checked it --- cleaning default.conf really helps. And C::B ready to use. Thanks.

However could you check the upgrade of .conf and etc. (.KeyBindings.ini) be performed well? Should I provide this file for that.
With my current .conf (with other name than default.conf) the /tmp/codeblocks_dbgrpt... looks like:

MortenMacFly:

--- Quote from: littlegene on December 27, 2013, 12:54:29 pm ---However could you check the upgrade of .conf and etc. (.KeyBindings.ini) be performed well? Should I provide this file for that.

--- End quote ---
Yes, please provide the conf file here as well. Most likely its related to the compiler framework being upgraded.

mark2:

--- Quote from: littlegene on December 27, 2013, 12:54:29 pm ---I've checked it --- cleaning default.conf really helps. And C::B ready to use. Thanks.

However could you check the upgrade of .conf and etc. (.KeyBindings.ini) be performed well? Should I provide this file for that. I will come back here later for more information.



--- End quote ---

I tried cleaning default.conf and it did help.  Thanks for that info.  

Navigation

[0] Message Index

[#] Next page