Opened 18 years ago
Closed 17 years ago
#422 closed bug (fixed)
[Bezeer] Segment violation
| Reported by: | diver | Owned by: | jackburton |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Kits/Interface Kit | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
Bezeer crash if you start it abd press Tools button in the welcome window.
GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-pc-haiku"...(no debugging symbols found)
Thread 347 caused an exception: Segment violation Reading symbols from /BeBox/apps/Beezer/lib/libCLV.so...(no debugging symbols found)...done. Loaded symbols for /BeBox/apps/Beezer/lib/libCLV.so Reading symbols from /boot/beos/system/lib/libbe.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libbe.so Reading symbols from /boot/beos/system/lib/libtracker.so... (no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtracker.so Reading symbols from /boot/beos/system/lib/libtranslation.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtranslation.so Reading symbols from /boot/beos/system/lib/libstdc++.hrev4.so... (no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libstdc++.hrev4.so Reading symbols from /BeBox/apps/Beezer/lib/libFSU.so...(no debugging symbols found)...done. Loaded symbols for /BeBox/apps/Beezer/lib/libFSU.so Reading symbols from /boot/beos/system/lib/libnet.so... (no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libnet.so Reading symbols from /boot/beos/system/lib/libroot.so...done. Loaded symbols for /boot/beos/system/lib/libroot.so Reading symbols from /boot/beos/system/lib/libsocket.so...done. Loaded symbols for /boot/beos/system/lib/libsocket.so
[Switching to team /BeBox/apps/Beezer/Beezer (341) thread popup (347)] 0x003d5fd0 in BView::Bounds () from /boot/beos/system/lib/libbe.so (gdb) bt #0 0x003d5fd0 in BView::Bounds () from /boot/beos/system/lib/libbe.so #1 0x003a6524 in BMenu::_show () from /boot/beos/system/lib/libbe.so #2 0x003a60df in BMenu::Show () from /boot/beos/system/lib/libbe.so #3 0x003a60b1 in BMenu::Show () from /boot/beos/system/lib/libbe.so #4 0x003b538e in BPopUpMenu::start_track ()
from /boot/beos/system/lib/libbe.so
#5 0x003b52d3 in BPopUpMenu::entry () from /boot/beos/system/lib/libbe.so #6 0x00719850 in thread_entry () from /boot/beos/system/lib/libroot.so #7 0x70080fec in ?? () (gdb)
Change History (6)
comment:1 by , 18 years ago
| Cc: | added |
|---|
comment:2 by , 18 years ago
| Owner: | changed from to |
|---|
comment:3 by , 18 years ago
| Description: | modified (diff) |
|---|---|
| Platform: | → All |
| Status: | new → assigned |
follow-up: 5 comment:4 by , 18 years ago
| Component: | General → User Interface/Interface Kit |
|---|---|
| Version: | → R1 development |
follow-up: 6 comment:5 by , 17 years ago
Replying to jackburton:
Since rev 19332 the original bug has been fixed. There's still a problem, but it doesn't seem related to menus.
comment:6 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Replying to jackburton:
Replying to jackburton:
Since rev 19332 the original bug has been fixed. There's still a problem, but it doesn't seem related to menus.
I spoke with the Beezer developer, and it looks like Beezer deletes the BPopUpMenu. Since the BPopUpMenu auto destroys itself, this leads to a segment violation (freeing already freed memory). I don't know why this doesn't happen under beos, but it's a Beezer bug. Closing.
I talked with the author, looks like that BPopUpMenu uses SetAsyncAutoDestruct(true) and it's opened with Go() synchronously. I think this case needs to be reviewed in our implementation. Another problem could be related to archiving/unarchiving.