Bug #18756 2012-10-16 18:20

zeroth

Crash on open certain projects.

I have only tested this on Linux. SVN info:

Path: .

URL: svn://svn.berlios.de/codeblocks/trunk

Repository Root: svn://svn.berlios.de/codeblocks

Repository UUID: 98b59c6a-2706-0410-b7d6-d2fa1a1880c9

Revision: 8458

Node Kind: directory

Schedule: normal

Last Changed Author: tpetrov

Last Changed Rev: 8457

Last Changed Date: 2012-10-16 04:31:22 -0400 (Tue, 16 Oct 2012)

edit: I'm new to this bug report system, still trying to figure out how to attach the bug report CodeBlocks generated.

Category
Application::Crash
Group
Platform:Linux
Status
Closed
Close date
2012-10-18 10:43
Assigned to
mortenmacfly
zeroth 2012-10-16 18:21

coudln't figure it out. I've uploaded it here:

http://www.bcaptain.net/bugreport.7z

mortenmacfly 2012-10-17 11:11

Cannot reproduce with the file attached...?!

zeroth 2012-10-17 18:00

here is a video of the crash, and also another crash report generated from it.

http://bcaptain.net/cb-crash.mpeg

http://bcaptain.net/report-from-video.7z

zeroth 2012-10-17 18:59

I've updated to SVN 8461. moved the clib.cbp file to a directory all by itself and renamed the original project directory *just in case* there were some absolute paths listed in the cbp. after I opened the isolated clib.cbp, it is still crashing.

zeroth 2012-10-17 19:08

I've discovered the line causing the issue. on the line

<Option compiler="gnu_gcc_compiler_462" />

if I change "gnu_gcc_compiler_462" to "gcc" it does NOT crash. I've also tried "gnu_gcc_compiler_461" since my version of gcc is 4.6.1 as reported by `gcc -v`, but that crashes also.

mortenmacfly 2012-10-18 10:43

Well you are not supposed to edit this file manually. If you do, crashes are expected.

I am closing this bug therefore.

zeroth 2012-10-18 15:21

I *didn't* edit the file. It was crashing from a stock *.cbp file generated by codeblocks 10.05. It was only *after* I first edited the file that it stopped crashing.

zeroth 2012-10-18 15:26

More than that, this is a crash bug. Which means there is something like a null deference, or a dangling pointer deference, or a buffer overflow, or something else nasty. And you call that Invalid?