Bugs item #894429, was opened at 2004-02-10 11:09
Message generated for change (Comment added) made by ajschult
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428680&aid=894429&group_id=40696

Category: Behaviour
Group: CVS
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Schultz (ajschult)
Assigned to: Nobody/Anonymous (nobody)
Summary: crash when switching workspaces

Initial Comment:
After switching workspaces, blackbox crashed.  I can't
reproduce the crash, but here's the stacktrace from the
core file:

#0  0x001e3c32 in _dl_sysinfo_int80 () from
/lib/ld-linux.so.2
#1  0x00356989 in raise () from /lib/tls/libc.so.6
#2  0x00358342 in abort () from /lib/tls/libc.so.6
#3  0x00350338 in __assert_fail () from /lib/tls/libc.so.6
#4  0x0805a352 in
BScreen::setCurrentWorkspace(unsigned) (this=0x83fbae0,
id=2)
    at Screen.cc:502
#5  0x080787bc in
bt::Application::process_event(_XEvent*) (this=0xbfe3f6e0, 
    event=0xbfe3f640) at Application.cc:353
#6  0x08075059 in Blackbox::process_event(_XEvent*)
(this=0xbfe3f6e0, 
    e=0xbfe3f640) at blackbox.cc:264
#7  0x080785a4 in bt::Application::run() (this=0xbfe3f6e0)
    at Application.cc:249
#8  0x08076bf1 in main (argc=1, argv=0xbfe3f8d4) at
main.cc:147
(gdb) frame 4
#4  0x0805a352 in
BScreen::setCurrentWorkspace(unsigned) (this=0x83fbae0,
id=2)
    at Screen.cc:502
502             win->show();
(gdb) p win
No symbol "win" in current context.


----------------------------------------------------------------------

Comment By: Andrew Schultz (ajschult)
Date: 2004-02-19 03:42

Message:
Logged In: YES 
user_id=312943

steps to reproduce:
1. add a workspace
2. remove the workspace
3. switch workspaces

#1 is probably not necessary...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428680&aid=894429&group_id=40696

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
List archives:  http://asgardsrealm.net/lurker/splash/index.html
Trouble? Contact [EMAIL PROTECTED]

Reply via email to