Recent Posts

Pages: 1 2 3 4 5 6 [7] 8 9 10
61
Development / Re: special handling of the macro replacement ""?
« Last post by ollydbg on February 24, 2026, 02:01:03 pm »
Any chance for noobs for the following?
   https://github.com/stahta01/CodeBlocks_Unofficial_Testing/blob/master/src/CodeBlocks_Windows_MSYS2.cbp

If I remember correctly. the msys2's wx library is shared library, so it has many separate libraries. I'm not sure it is easy to add to gd_on's cbp.
62
Development / Re: special handling of the macro replacement ""?
« Last post by Wkerry on February 24, 2026, 11:10:52 am »
Any chance of getting the following in once update to make the cbp's consistent as this will also reduce the cbp quantity?
     https://github.com/stahta01/CodeBlocks_Unofficial_Testing/blob/master/src/CodeBlocks_Unix_MacOS.cbp

Any chance for noobs for the following?
   https://github.com/stahta01/CodeBlocks_Unofficial_Testing/blob/master/src/CodeBlocks_Windows_MSYS2.cbp
63
General (but related to Code::Blocks) / Re: Someone on Reddit can't register to forums
« Last post by ParduzGM on February 23, 2026, 07:20:08 pm »
Maybe, he could change his email address and register again.
Thankyou.

gmail.com worked, yahoo.it still does not. I would like to the other one, if possible.

Anyway, thank to you both.
64
We can have several steps:
1, keep the old(existing) cbps and add the new unified windows cbps to the svn repo.
2, wait for several months.
3, finally those old cbps should be removed.
65
I lot of tools help me to find the crash/assert.

1, gd_on's unified code::blocks cbp/workspace files(gerard-durand/codeblocks_gd_cbps: Workspace and projets files to build Code::Blocks for Windows as a wxWidgets version independant), I can simply change the option so it links to the debug version of the wx 3.3.1, just change a global compiler variable wxWidgets.WX_SUFFIX from "u" to "ud". Without this unifiled cbp, I think I need a lot of changes.

2, gdb(I'm currently using ssbssa/gdb: Unofficial Windows build of gdb with added features., I think other gdbs are all good)can catch such crash call stack.

66
General (but related to Code::Blocks) / Re: Someone on Reddit can't register to forums
« Last post by ollydbg on February 23, 2026, 04:23:27 am »
https://www.reddit.com/r/codeblocks/comments/1r8vgpr/is_codeblocks_still_alive/

Thanks for the report.

Maybe, he could change his email address and register again.

If that still failed, I think I will wrote an email to our web admin to check whether the email system works or not.

Note the email notification(our the forum thread) works OK.
67
@ ollydbg

Thank you for that traceback. It spots the errror.
I can be so dumb sometimes. I remember that I copied that code from the original testing "prob of LSP" and told my self I'd need to revisit later. Then I forgot.


I'll fix it to use cross thread communication.
68
Another issue is the payload.

Code
e.SetPayload<std::string*>(&stdstr);
m_notifiedWindow->ProcessEvent(e);

We can not pass the local variable's address from the worker thread to the GUI thread, we should bring the whole std::string instead.
70
When I looked at the #6 of the call stack, I see this:

Code
                            if(!buffErr.IsEmpty() && m_notifiedWindow) {
                                // we got some data, send event to parent
                                //clProcessEvent e(wxEVT_ASYNC_PROCESS_STDERR);
                                wxThreadEvent e(wxEVT_ASYNC_PROCESS_STDERR, wxID_NONE);
                                //wxString& b = const_cast<wxString&>(e.GetOutput());
                                //b.swap(buffErr);
                                //e.SetProcess(m_process);
                                //m_notifiedWindow->AddPendingEvent(e);
                                //-std::string stdstr = buffErr.ToStdString(); loses data
                                #if wxCHECK_VERSION(3,1,5)
                                std::string stdstr = buff.utf8_string();
                                #else
                                std::string stdstr =  buff.ToStdString(wxConvUTF8);
                                #endif
                                e.SetPayload<std::string*>(&stdstr);
                                m_notifiedWindow->ProcessEvent(e);
                            }

It shows this statement: m_notifiedWindow->ProcessEvent(e);

So, this is a working thread, is it possible to call the ProcessEvent event from the working thread? I think it should be "PostEvent" or "QueueEvent". Am I correct?
Pages: 1 2 3 4 5 6 [7] 8 9 10