Anything from wxMessageDialog to wxFileDialog seg faults as soon as it tries to open. Even using dialog code taken from the source code's examples still seg faults when I try to open it. I've tried both the Apt repo version, as well as building both the stable and latest builds myself with a myriad of configurations. Running the debugger makes something about "/build/glibc-SzIz7B/glibc-2.31/sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S" pop up, but that's the most I could find about the error. Here is an example of the code that causes a segfault:
wxMessageDialog *dial = new wxMessageDialog(this, wxT("Download completed"), wxT("Info"), wxOK);
wxFileDialog* openFileDialog = new wxFileDialog(this, _("Open XYZ file"), "", "",
"XYZ files (*.xyz)|*.xyz", wxFD_OPEN|wxFD_FILE_MUST_EXIST);
I am at a complete loss. Some of these are taken directly from tutorials or the source code. The most I found about it online was from 2006, and just said to recompile.
Platform and version information
wx-config --version-full: 3.0.5.0 (the most recent one I tried)—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Sorry, GCC version: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Please get the latest release from wxwidgets.org download page, build it using --enable-debug and try to run the dialogs sample.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Closed #22523 as not planned.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Sorry but I think that the problem must be due to a "myriad of configurations". Please make sure to build one, and only one, build of the library and the same headers and, of course, compiler and compiler options to build both the library and your application. Only mixing them up can result in "impossible" crashes like this -- the samples definitely don't crash when opening a dialog.
Sorry but we can't help you find the problem, only you can solve it by
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()