Kismet Wireless

Kismet Forums

 

Posted by:tecjnology
Subject:Newcore Client Window
Date:09:00:02 29/05/2010

I've had the same problem lately, here is the bt output after crtl-c:

Program received signal SIGINT, Interrupt.
0x080964ae in Kis_Menu::FindNextEnabledItem (this=0x81f0a38) at kis_panel_widgets.cc:1342
1342 if (i >= (int) menubar[cur_menu]->items.size())
(gdb) bt
#0 0x080964ae in Kis_Menu::FindNextEnabledItem (this=0x81f0a38) at kis_panel_widgets.cc:1342
#1 0x08098da2 in Kis_Menu::KeyPress (this=0x81f0a38, in_key=261) at kis_panel_widgets.cc:1533
#2 0x08096d58 in Kis_Panel::KeyPress (this=0x81f2800, in_key=261) at kis_panel_widgets.cc:3438
#3 0x0809752d in Kis_Panel::Poll (this=0x81f2800) at kis_panel_widgets.cc:3593
#4 0x08097ff9 in PanelInterface::Poll (this=0x81b2bb0, in_rset=..., in_wset=...) at kis_panel_widgets.cc:334
#5 0x0817fc9c in main (argc=1, argv=0xbffff414, envp=0xbffff41c) at kismet_client.cc:398
(gdb) quit





> > I've noticed that when I open the Clients window, many times I'm unable to close that window to go back to the network view. Kismet seems to lock up instead (or at least locks to that window only). My kismet build is whatever was in SVN on May 4th and the OS is Backtrack 4 final, although the problem was present on older builds that I was running. I'm also using several computers (in a classroom) so I don't think it is a hardware problem.
> >
> > Is this a known bug or am I doing something wrong? If you need some kind of debugging info, just let me know what info you would like.
>
> I can't seem to recreate it... I'll try some more though.
>
> If you can get it to hang while in gdb, hit control-c and run 'bt' to get a backtrace and tell me what function it's falling down in.
>
> >
> > Thank you...
> >
> > regards,
> >
> > cybrsnpr


Reply to this message