User forums > Nightly builds

The 01 November 2012 build (8497) is out.

<< < (2/7) > >>

ollydbg:

--- Quote from: ironhead on November 01, 2012, 10:22:52 pm ---This build crashes as soon as I go to Settings > Editor...

I'm running Windows 7 Pro 32-bit.

--- End quote ---
Tested, I do not have the crash. (WinXP).
I guess your configure file(default.conf) was broken, can you try to delete the conf file, and try again?

Jenna:
8497 does not crash at least not in debugger), but gives me the following output:

--- Quote ---$compiler $options $includes -c $file -o $object
$linker $libdirs -o $exe_output $link_objects $link_resobjects $link_options $libs
/bin/sh: -c: command not found
Process terminated with status 127 (0 minutes, 0 seconds)
0 errors, 0 warnings (0 minutes, 0 seconds)
Build log saved as:
file:///tmp/test/test_build_log.html
 

--- End quote ---

No macro replacement, looks like broken compiler lookup again.

MortenMacFly:

--- Quote from: jens on November 02, 2012, 02:04:39 am ---No macro replacement, looks like broken compiler lookup again.

--- End quote ---
Program received signal SIGSEGV, Segmentation fault.
0x61e5e8b2 in DirectCommands::GetCompileSingleFileCommand (this=0x22ed18,
    filename=...)
    at C:/Devel/CodeBlocks/src/plugins/compilergcc/directcommands.cpp:342
→→C:\Devel\CodeBlocks\src\plugins\compilergcc\directcommands.cpp:342:11849:beg:0x61e5e8b2

Reproducible... I'll see what I can do.

Jenna:

--- Quote from: MortenMacFly on November 02, 2012, 08:11:38 am ---
--- Quote from: jens on November 02, 2012, 02:04:39 am ---No macro replacement, looks like broken compiler lookup again.

--- End quote ---
Program received signal SIGSEGV, Segmentation fault.
0x61e5e8b2 in DirectCommands::GetCompileSingleFileCommand (this=0x22ed18,
    filename=...)
    at C:/Devel/CodeBlocks/src/plugins/compilergcc/directcommands.cpp:342
→→C:\Devel\CodeBlocks\src\plugins\compilergcc\directcommands.cpp:342:11849:beg:0x61e5e8b2

Reproducible... I'll see what I can do.

--- End quote ---

Simple cause:
in directcommands.cpp:57, the pointer to the command-generator is initialised, but if there is no project, this line will never be reached.
Just moving the code from line 57 to the beginning of the ctor, works here on linux.
Can you test it on windows ?
A change should be committed with a small comment.

EDIT:
the issue must be there since r8457, if I see it correctly.

MortenMacFly:

--- Quote from: softred on November 01, 2012, 11:34:43 pm ---When I compile a c++ source file without project a have a crash, the log only prints "Aborted".

--- End quote ---


--- Quote from: jens on November 02, 2012, 09:01:14 am ---Just moving the code from line 57 to the beginning of the ctor, works here on linux.
Can you test it on windows ?

--- End quote ---
Tried, works, and committed. This was an "ooopsi" error when changing the command generation interface for CC.

Thanks for the report!

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version