User forums > General (but related to Code::Blocks)
wxWidgets 3.1.5
gd_on:
In parallel, I had signaled this behaviour on wxtrac.
Here is their answer :
--- Quote ---Comment (by MaartenB):
FYI, it was added in https://github.com/wxWidgets/wxWidgets/pull/2169
Apparently you call `wxChoice::GetString()` with invalid index `-1`. The
behaviour is also documented in
https://docs.wxwidgets.org/trunk/classwx_choice.html#a3a89e3eef072e7914f8408154b4a1daa
--
Ticket URL: <https://trac.wxwidgets.org/ticket/19096#comment:3>
--- End quote ---
So, for them, there is a call to GetString with incorrect value.
Miguel Gimenez:
That was clear, the problem is finding where the call is, and the stack trace is the guide.
EDIT: can you try starting C::B from command line using --safe-mode switch?.
gd_on:
running codeblocks from the command line give this :
* without option : give the message; Nothing seems to be created (no log, no txt file), but may be I should use a C::B code compiled with -g and also perhaps wxwidgets).
* with --safe-mode : no message.
gd_on:
I tried to disable plugins and re-enable them one by one.
The guilty seems to be FileManager plugin : no message if it is disabled alone, all other activated.
Miguel Gimenez:
Now I can reproduce, this is the stack trace:
--- Code: ---#0 0x62da1cb8 in wxChoice::GetString(unsigned int) const () from C:\Windows\system32\wxmsw315u_gcc_custom.dll
#1 0x6c32422f in FileExplorerUpdater::Update (this=0x20572958, ti=...)
at G:\cbtrunk\src\plugins\contrib\FileManager\FileExplorerUpdater.cpp:153
#2 0x6c30a1ba in FileExplorer::OnTimerCheckUpdates (this=0x205c07e0)
at G:\cbtrunk\src\plugins\contrib\FileManager\FileExplorer.cpp:594
#3 0x62a43222 in wxAppConsoleBase::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const ()
from C:\Windows\system32\wxmsw315u_gcc_custom.dll
#4 0x0028d57c in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version