Ubuntu 11.10 (oneiric) 64 bits, wxWidgets 2.8.12, code::blocks svn 7899
If I try to add a bitmap button to any container, the program crashes, opening a totally blank crash report window (nothing on it except the window system close button). If I close it the program closes and any changes are lost.
Any suggestions?
TIA,
Ken
Quote from: kencamargo on March 19, 2012, 03:00:58 AM
Ubuntu 11.10 (oneiric) 64 bits, wxWidgets 2.8.12, code::blocks svn 7899
If I try to add a bitmap button to any container, the program crashes, opening a totally blank crash report window (nothing on it except the window system close button). If I close it the program closes and any changes are lost.
I managed to get one bug report, sending attached as a .zip file, in the hope this helps.
Again, thanks for any help,
Ken
Quote from: kencamargo on March 19, 2012, 04:00:02 AM
Quote from: kencamargo on March 19, 2012, 03:00:58 AM
Ubuntu 11.10 (oneiric) 64 bits, wxWidgets 2.8.12, code::blocks svn 7899
If I try to add a bitmap button to any container, the program crashes, opening a totally blank crash report window (nothing on it except the window system close button). If I close it the program closes and any changes are lost.
I managed to get one bug report, sending attached as a .zip file, in the hope this helps.
Whatever it was, it's gone in the new nightlie.
Quote from: kencamargo on March 26, 2012, 10:57:39 PM
Quote from: kencamargo on March 19, 2012, 04:00:02 AM
Quote from: kencamargo on March 19, 2012, 03:00:58 AM
Ubuntu 11.10 (oneiric) 64 bits, wxWidgets 2.8.12, code::blocks svn 7899
If I try to add a bitmap button to any container, the program crashes, opening a totally blank crash report window (nothing on it except the window system close button). If I close it the program closes and any changes are lost.
I managed to get one bug report, sending attached as a .zip file, in the hope this helps.
Whatever it was, it's gone in the new nightlie.
It's been back for a while. I've upgraded both Ubuntu and codeblocks, and the problem persists. Last time it generated a report in Ubuntu, the error seems to be trying to access an invalid memory area. Is there a default bitmap that is used? COuld the path to it be corrupted on an installation?
Quote from: kencamargo on July 14, 2012, 02:12:39 AM
It's been back for a while. I've upgraded both Ubuntu and codeblocks, and the problem persists. Last time it generated a report in Ubuntu, the error seems to be trying to access an invalid memory area. Is there a default bitmap that is used? COuld the path to it be corrupted on an installation?
After updating: Ubuntu 12.04 (precise) 64 bits, wxWidgets 2.8.12, code::blocks svn 8059 (from pasgui; got the same with jen's)
Repeating the issue:
If I try to add a bitmap button to any container, the program crashes, opening a totally blank crash report window (nothing on it except the window system close button). If I close it the program closes and any changes are lost.
Examining my install, I found a local (under $HOME) directory called .codeblocks, under which there was a /share/codeblocks/scripts directory; it contained just one file, startup.script, which duplicated /usr/share/codeblocks/startup.script; i eliminated the version under the local dir and apparently the problem is solved. I wonder if the local directory should exist at all.
Nope, that was not it, happening again. If someone could please help me, I'd be immensely grateful, this is driving me nuts.
Quote from: kencamargo on July 14, 2012, 05:10:30 AM
Nope, that was not it, happening again. If someone could please help me, I'd be immensely grateful, this is driving me nuts.
I get it too using the new code blocks with wxpack. I can use the old version nightly 8500 and I do not get a crash when adding a bitmap button. Is there any fix for this?
Quote from: papayrus on March 01, 2013, 09:27:55 AM
Quote from: kencamargo on July 14, 2012, 05:10:30 AM
Nope, that was not it, happening again. If someone could please help me, I'd be immensely grateful, this is driving me nuts.
I get it too using the new code blocks with wxpack. I can use the old version nightly 8500 and I do not get a crash when adding a bitmap button. Is there any fix for this?
I still get it. New machine, Ubuntu 12.10 64 bits, code::blocks 12.11. The workaround I found is that if you open the wxSmith layout file but change the tab on the management pane to something other than "Resources", you can add the wxBitmapButton without a crash, but you have to:
a) add the wxBitmapButton to the layout;
b) save everything;
c) close the layout file;
d) re-open the layout file so that you can work on the element you just added. Not particularly convenient.
I am using Windows7 and wxWidgets(same version I think) and I have the same problem.If you add a bitmap button when the "Resources" tab is selected,or if you add the bitmap button and then select "Resources" tab, Codeblocks crashes...
Quote from: Awareness on March 04, 2013, 09:34:20 PM
I am using Windows7 and wxWidgets(same version I think) and I have the same problem.If you add a bitmap button when the "Resources" tab is selected,or if you add the bitmap button and then select "Resources" tab, Codeblocks crashes...
At least now I know I'm not crazy. :)
Works here, gentoo linux r8897.
Please describe the exact steps to reproduce the problem.
If you provide a sample project one step from the crash might help, too.
Edit: talked too early, I've made it crash, by placing the button inside a panel.
Quote from: oBFusCATed on March 05, 2013, 12:49:01 AM
Works here, gentoo linux r8897.
Please describe the exact steps to reproduce the problem.
If you provide a sample project one step from the crash might help, too.
Edit: talked too early, I've made it crash, by placing the button inside a panel.
Steps:
- use the wizard to create a new dialog-based wxWidgets project;
- open the dialog layout for editing with wxSmith;
- add a wxBitmapButton to the dialog, anywhere;
- BOOM.
The project one step from crashing is the initial project created with Project|New.
This is a pretty strange issue :(
This is the bt from my installed version of C::B
(gdb) bt
#0 0x00007ffff7a9f964 in wxBoolProperty::GetValueAsString(int) const () from /usr/lib64/libcodeblocks.so.0
#1 0x00007ffff7a7f8c0 in wxPGProperty::GetValueString(int) const () from /usr/lib64/libcodeblocks.so.0
#2 0x00007ffff7a801e1 in wxPGDefaultRenderer::Render(wxDC&, wxRect const&, wxPropertyGrid const*, wxPGProperty*, int, int, int) const () from /usr/lib64/libcodeblocks.so.0
#3 0x00007ffff7a911dd in wxPropertyGrid::DoDrawItems(wxDC&, wxPGProperty const*, wxPGProperty const*, wxRect const*, bool) const () from /usr/lib64/libcodeblocks.so.0
#4 0x00007ffff7a91bbc in wxPropertyGrid::DrawItems(wxDC&, unsigned int, unsigned int, wxRect const*) () from /usr/lib64/libcodeblocks.so.0
#5 0x00007ffff7a920a7 in wxPGCanvas::OnPaint(wxPaintEvent&) () from /usr/lib64/libcodeblocks.so.0
#6 0x00007ffff5da9e26 in wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) () from /usr/lib64/libwx_baseu-2.8.so.0
#7 0x00007ffff5da9fab in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) () from /usr/lib64/libwx_baseu-2.8.so.0
#8 0x00007ffff5daa2e4 in wxEvtHandler::ProcessEvent(wxEvent&) () from /usr/lib64/libwx_baseu-2.8.so.0
#9 0x00007ffff6449c40 in wxWindow::GtkSendPaintEvents() () from /usr/lib64/libwx_gtk2u_core-2.8.so.0
#10 0x00007ffff644a108 in ?? () from /usr/lib64/libwx_gtk2u_core-2.8.so.0
#11 0x00007ffff57be618 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0
#12 0x00007ffff54414f3 in g_closure_invoke () from /usr/lib64/libgobject-2.0.so.0
This seems like a wxPropGrid issue...
I was not able to reproduce the crash, when I tried with C::B and wxSmith compiled inside C::B :(
Pretty strange.
Edit: Running optimized builds is enough to reproduce the crashes, still no clue where is the problem :(
Quote from: oBFusCATed on March 05, 2013, 01:10:06 AM
This is a pretty strange issue :(
(snip)
Edit: Running optimized builds is enough to reproduce the crashes, still no clue where is the problem :(
At least now other people are having the same trouble, for almost an year I was resigned to this being some sort of private curse... I can try to generate an error report again, the problem being that 9 times out of ten the report itself got wiped out.
Is there anyway to fix this yet?
I won't be able for the next two-three weeks... and this is really hard issue, because it is pretty random -> it might be anything that is broken.
I can't reproduce the crash. I'm using Unofficial C::B release Unofficial Code::Blocks installer for Windows (svn 8896) (http://forums.next.codeblocks.org/index.php/topic,13234.msg88948.html#msg88948) under Windows XP.
ollydbg: debug or release build of C::B are you using? This happens only in release build, turn of optimizations and it is done.
Quote from: oBFusCATed on March 13, 2013, 03:56:54 AM
ollydbg: debug or release build of C::B are you using? This happens only in release build, turn of optimizations and it is done.
Typos in your post: of->off, done->gone.
I'm not sure, I should ask ptDev (http://forums.next.codeblocks.org/index.php?action=profile;u=12671), BTW: I never build a "-O2" version of C::B myself. :)
I don't recall ever changing the default target or its settings in most plugin projects.
I certainly never did that with wxSmith, so it probably is indeed getting compiled without optimizations.
Post build, I do try to reduce the executables size by both removing their symbols and compressing them.
It goes without saying, if anyone does get a crash with my binaries, they should try to reproduce it with the nightly build instead. While I try to keep my local changes to a minimum, there are enough of them to warrant not using my build as a representation of the state of the trunk.
I have the same problem with C::B 12.11 with MinGW. Everytime I try to add a bitmap button, codeblocks crashes. Hiding the resources tab helps at first but I can't do anything without the resources. As soon as I try to ad a bitmap it crashes again.
I switched back to version 10.05 so at least I could finish my work. Would be nice if there was a patch for this as the new C::B has a lot more features.
Yes what he said above it happens in 12.11 and it happens when you add a bitmap button then change to another tab besides resources. You can add all your bitmap buttons while a different tab is on then save the project and close it then reopen it and as long as you dont add any more bitmap buttons it works fine.
The cause for the issue seems to be an unitialised bool member-variable used with WXS_BOOL-macro.
It should be fixed in trunk (svn r9023).
Can anyone with this issue test it and give feedback ?
Can confirm that this works with rev 9114 (windows, built from svn)
This did not work for me with rev 8629