I am experiencing pseudorandom crashing in what seems like any 1.0.x
version of fluxbox; 0.9.x was ok. I rebuilt my fluxbox from source with
debug info turned on, and made some cores; I get crashing several times
a day every day, so these are easy to get. I have many windowmanager
functions (window switching, minimize, maximize, etc) mapped to
keyboard shortcuts using the Window-key. About a third of the crashes
happen when I release the window button, having just completed a few
window operations.
Also of note is that my .fluxbox/keys contains
Mod4 Tab :NextWindow 23
Shift Mod4 Tab :PrevWindow 23
I mapped my Window-Tab with option 23 to not cycle through minimized
windows, among other things. Many of these crashes happen in
FocusControl::stopCyclingFocus(). Seems like client->fbwindow() can be
a bogus pointer in
if (m_cycling_window != it_end && client &&
client->fbwindow()->isVisible()) {
m_focused_list.remove(client);
m_focused_list.push_front(client);
client->fbwindow()->raise();
Sadly this doesn't mean that client->fbwindow() is NULL, since adding
that to the above if() list didn't fix the crashing. With that
modification I got the crash:
#0 0x00002b16ff607635 in raise () from /lib/libc.so.6 #1
0x00002b16ff609090 in abort () from /lib/libc.so.6 #2
0x000000000041bc26 in Fluxbox::handleSignal (this=0x76f090, signum=0)
at fluxbox.cc:1119
#3 <signal handler called>
#4 FluxboxWindow::isVisible (this=0x1ffffffff) at Window.cc:3660
#5 0x00000000004972e5 in FocusControl::stopCyclingFocus (this=0x7a7b80)
at FocusControl.cc:207
#6 0x00000000004ceb73 in FbTk::EventManager::ungrabKeyboard
(this=0x7492c0) at EventManager.cc:86
#7 0x00000000004cee0e in FbTk::EventManager::dispatch (this=0x7492c0,
win=122, [EMAIL PROTECTED], parent=<value optimized out>)
at EventManager.cc:179
#8 0x000000000041be3c in Fluxbox::handleEvent (this=0x76f090,
e=0x7fffacd2e100) at fluxbox.cc:743
#9 0x000000000041c6eb in Fluxbox::eventLoop (this=0x76f090) at
fluxbox.cc:560 #10 0x0000000000431a3c in main (argc=1,
argv=0x7fffacd2e6a8) at main.cc:291
Here client->fbwindow() returned 0x1ffffffff. Putting that into the
list didn't cure it either. There are still multitudes of other
crashing that isn't related to the keyboard it seems. Example:
#0 0x00002b773f377635 in raise () from /lib/libc.so.6
#1 0x00002b773f379090 in abort () from /lib/libc.so.6
#2 0x000000000041bc26 in Fluxbox::handleSignal (this=0x76f090,
signum=0) at fluxbox.cc:1119 #3 <signal handler called>
#4 Gnome::updateClientList (this=0x7df8a0, [EMAIL PROTECTED])
at /usr/include/c++/4.1.3/bits/stl_list.h:223 #5 0x00000000004198a9 in
Fluxbox::update (this=0x76f090, changedsub=<value optimized out>) at
fluxbox.cc:1225 #6 0x00000000004f7767 in
std::for_each<std::_List_iterator<FbTk::Observer*>,
std::binder2nd<std::mem_fun1_t<void, FbTk::Observer, FbTk::Subject*> >
> (__first=<value optimized out>, __last={_M_node = 0x77a048}, __f=
> {<std::unary_function<FbTk::Observer*,void>> = {<No data fields>}, op
> = {<std::binary_function<FbTk::Observer*,FbTk::Subject*,void>> = {<No
> data fields>}, _M_f = <error reading variable>}, value = 0x77a038})
> at /usr/include/c++/4.1.3/bits/stl_function.h:656 #7
> 0x00000000004f7083 in FbTk::Subject::notify (this=0x77a038) at
> Subject.cc:63
#8 0x0000000000437853 in BScreen::updateNetizenWindowAdd
(this=0x77a020, w=9637408, p=0) at Screen.cc:1323 #9
0x0000000000470b47 in Workspace::addWindow (this=0x7ab640, w=<value
optimized out>, place=false) at Workspace.cc:189 #10 0x000000000046e3b0
in FluxboxWindow::init (this=0x8320c0) at Window.cc:512 #11
0x000000000046e9f2 in FluxboxWindow (this=0x8320c0, [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]) at Window.cc:282 #12 0x000000000043935e
in BScreen::createWindow (this=0x77a020, client=<value optimized out>)
at Screen.cc:1472 #13 0x000000000041c539 in Fluxbox::handleEvent
(this=0x76f090, e=0x7fff6cfbe390) at fluxbox.cc:810 #14
0x000000000041c6eb in Fluxbox::eventLoop (this=0x76f090) at
fluxbox.cc:560 #15 0x0000000000431a3c in main (argc=1,
argv=0x7fff6cfbe938) at main.cc:291
If anybody has ideas, please let me know. As I said, fluxbox is very
unstable on my machine and I'can easily generate cores.
Thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
