User forums > Announcements

Preparing Code::Blocks Release

<< < (6/13) > >>

killerbot:
Hey Tim,

could you explain why the dll that now is build with the nightlies is not ok ?

stahta01:

--- Quote from: killerbot on March 31, 2010, 07:57:57 am ---Hey Tim,

could you explain why the dll that now is build with the nightlies is not ok ?

--- End quote ---

The dll is involved in producing the crash report. Without the DLL matching the MiNGW GCC version the report is missing words/alpha and is just mainly numbers and shorter than it should be.

In other words the debug info format changed. It should work if the debug format was the same for DLL and MinGW GCC.

The compilers you used in the past was broken or used Dwarf2; I have not tried lately to see if the issue still exists.

Tim S.

MortenMacFly:

--- Quote from: stahta01 on March 31, 2010, 04:08:22 pm ---The compilers you used in the past was broken or used Dwarf2; I have not tried lately to see if the issue still exists.

--- End quote ---
Usually every MinGW/GCC compiler released ships with its own version of exchndl.dll. So all you need to do is to use the same compiler for compiling wxWidgets and Code::Blocks and then ship the right version of the exchndl.dll. I am aware that we have an old version in the repo which is compatible for MinGW 3.4.5 only. For the release we will should use the right one. But I don't think we really need to compile this ourselves...?! :shock:

thomas:
I think you should copy the one that's coming with whatever compiler you use. Or, we should see if we can do without it (not quite sure what compiler flag would be needed for that).
If I remember correctly this DLL's sole purpose is to run some code at DLL_THREAD_ATTACH and DLL_THREAD_DETACH, which supposedly makes sure that heap memory allocated by exceptions is freed properly in multi-threaded contexts. Yeah, whatever :)

Exceptions should not happen very often anyway (hopefully), so I'm almost inclined to say "so what". I'm not even sure we throw anywhere at all, or whether that's heap-allocated.

oBFusCATed:

--- Quote from: thomas on April 01, 2010, 10:06:54 am ---Exceptions should not happen very often anyway (hopefully), so I'm almost inclined to say "so what". I'm not even sure we throw anywhere at all, or whether that's heap-allocated.

--- End quote ---
Executing scripts can throw...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version