Kismet Wireless

Kismet Forums


Posted by:TheDude
Subject:WiSpy on OSX
Date:02:08:10 17/03/2006

I can confirm this. using an intel x86 imac with fink's GTK2 and libusb installed.

it fails with:
wispy_gtk: Write error on IPC to gui: No buffer space available
wispy_gtk: Failed to read signal data.

compile warnings are:
wispy_gtk.c: In function 'graph_configure_event':
wispy_gtk.c:743: warning: pointer targets in passing argument 3 of 'gdk_gc_set_dashes' differ in signedness
wispy_gtk.c:757: warning: pointer targets in passing argument 3 of 'gdk_gc_set_dashes' differ in signedness
wispy_gtk.c: In function 'IPC_Service_Loop':
wispy_gtk.c:1133: warning: incompatible implicit declaration of built-in function 'memset'

this is using gcc 4.0.1

Id be happy to help track this down. if theres anything i could do, let me know.

> > My WiSpy just came in, and I have a question regarding your tools in OSX.
> >
> > I was able to successfully build the binaries without much difficulty against the libusb, curses, and gtk2 libraries supplied by fink. Both wispy_raw and wispy_curses appear to start up and receive data from the WiSpy. However, when wispy_gtk starts up it exits immediately after the window pops open, and gives the error "wispy_gtk: Failed to read signal data." Any ideas why that one utility might not be able to read incoming data while the others can do it just fine?
> They ought to all access it the same way. That particular error is due to the IPC communication between the process that reads the data and the process that provides the UI. It's possible that OSX doesn't block on read for some reason, but I don't know since I don't have an osx box for testing and no-one else has reported it.
> -m

Reply to this message