Recent Posts

31

Using Code::Blocks / Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

« Last post by ollydbg on January 28, 2026, 08:41:34 am »

With the help of some AI, I think I have got the idea, but I'm not tested yet.

See here:

https://github.com/wxWidgets/wxWidgets/issues/26108#issuecomment-3809535580

It looks like we have to set a member variable in the override functions.

BTW: VZ(wx developer) just thought that the crash should not happen, but In my test case, if run without the debugger, the assert just cause the crash, not sure why. Any ideas?

32

Development / special handling of the macro replacement ""?

« Last post by ollydbg on January 28, 2026, 06:43:08 am »

Hi, when I'm using the gd_on's unified workspace/code::blocks cbp files, I see something strange.

See here: it looks like GCC works OK, but GDB failed to find the dll(setting wrong PATH)

Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

If a variable a has a filed name b, and its value is

Code

""

, and if we have

Code

AAA$(#a.b)

, we will finally get

Code

AAA""

The current implementation treats an empty string "" as a valid value and performs the replacement, resulting in

Code

AAA""

instead of the expected

Code

AAA

.

I'd like to see your options on this issue.

Thanks.

33

Using Code::Blocks / Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

« Last post by ollydbg on January 27, 2026, 08:26:48 am »

Code

#if WXWIN_COMPATIBILITY_3_2
// By call to obsolete function we want to check if user-overriden function is still in use
wxString wxPGProperty::ValueToStringWithCheck(wxVariant& variant, wxPGPropValFormatFlags flags) const
{
    m_oldValueToStringCalled = false;
    wxString res = ValueToString(variant, static_cast<int>(flags));
    if ( m_oldValueToStringCalled )
    {
        // Our own function was called - this implies that call was forwarded to the new overriding
        // function and there is no need to call it explicitly.
    }
    else
    {   // User-overriden obsolete function was called
        wxFAIL_MSG(wxString::Format("in %s use ValueToString with 'flags' argument as wxPGPropValFormatFlags", GetClassInfo()->GetClassName()));
    }
    return res;
}
#endif // WXWIN_COMPATIBILITY_3_2

In the call stack frame 2, this function always cause assert, do you see this? I have update comments in github issue: https://github.com/wxWidgets/wxWidgets/issues/26108#issuecomment-3803542263

34

Using Code::Blocks / Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

« Last post by ollydbg on January 27, 2026, 08:11:28 am »

Not extensivety tested, but it looks OK : wxs files are opened without crash.
Thanks

I try to build a debug version of wx 3.3.1 library, and later build C::B against this library.

When I try to run the debugging, I see this:

Code

Active debugger config: GDB/CDB debugger:Default
Selecting target: 
src
Adding source dir: F:\code\codeblocks-src\codeblocks_sfmirror\src\
Adding source dir: F:\code\codeblocks-src\codeblocks_sfmirror\src\
Adding file: F:\code\codeblocks-src\codeblocks_sfmirror\src\devel33_64\codeblocks.exe
Changing directory to: F:/code/codeblocks-src/codeblocks_sfmirror/src/devel33_64
Set variable: PATH=.;F:\code\wxWidgets-3.3.1\lib\gcc_dll"";F:\code\codeblocks-src\codeblocks_sfmirror\src\devel33_64;F:\code\codeblocks-src\codeblocks_sfmirror\src\exchndl\win64\lib;...

Then, it said the wx dll can't be find, so the debugee C::B can't started.

But if you looked at this:

Code

F:\code\wxWidgets-3.3.1\lib\gcc_dll""

You see the trailing quotes, this quotes come from some global compiler variable those values are "".
It works OK when in compiling, I see such things when compiling:

Code

[100.0%] g++.exe -shared  -Wl,--out-implib=devel33_64\libcodeblocks.a -Wl,--dll 
-LF:\code\wxWidgets-3.3.1\lib\gcc_dll"" 
-Ldevel33_64 

Now, here is the crash call stack, I put it in the txt file in attachment.

35

Using Code::Blocks / Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

« Last post by ollydbg on January 27, 2026, 03:53:19 am »

I think I have reported the same issue here in 2025-09, see this post:

Re: code::blocks hangs at startup

So, this issue lasts for a long time.

36

Using Code::Blocks / Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

« Last post by ollydbg on January 27, 2026, 02:37:27 am »

Not extensivety tested, but it looks OK : wxs files are opened without crash.
Thanks

Strange, I just replaced my local the file: wxscolourproperty.cpp, but the result C::B still crash with the same issue.

37

Using Code::Blocks / Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

« Last post by gd_on on January 26, 2026, 07:49:43 pm »

Not extensively tested, but it looks OK : wxs files are opened without crash.
Thanks

38

Using Code::Blocks / Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

« Last post by Miguel Gimenez on January 26, 2026, 06:22:09 pm »

Try this file (rename as cpp). It may need some adjustment to compile on wx3.3.

39

Using Code::Blocks / Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

« Last post by Miguel Gimenez on January 26, 2026, 04:38:05 pm »

This method, defined in wxscolourproperty.cpp:152

Code

    wxString wxsMyColourPropertyClass::ValueToString( wxVariant& value,  int argFlags ) const

does not override in wx >= 3.3.0 because the second parameter is no longer an integer, see the documentation.

EDIT: Adding "override" to the declaration would have uncovered this long ago.

40

Using Code::Blocks / Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

« Last post by ollydbg on January 26, 2026, 03:58:06 pm »

It looks like the C::B try to read some string values to "reconstruct" the prop grid when reading the wxs file.

But the "string value" maybe empty or not correct, so wx just report the assert.

My guess is that the issue is inside the wxWidgets' library code, not in the C::B's source code.