Continuous Crashes on OSX v10.11.6 (El Capita)
An OS X client for the Nordic BTLE sniffer dongle.
Brought to you by:
rolandking
Menu
▾
▴
1 Attachments
#14 Continuous Crashes on OSX v10.11.6 (El Capita)
Hello Roland,
Thanks for your support on the ticket https://sourceforge.net/p/nrfblesnifferosx/tickets/13/. I couldn't reply you there and that's why writing here.
Following your reply i have found out that i was not clickin "sniff device" before clicking "capture wireshark".
Another thing is that when i installed ble-sniffer-osx(v1.2.4) it installed bso_nordic_btle.so under ~/.wireshark/pluings and wireshark (v2.05) is looking for plugins at ~/.config/wireshark/plugins. That is why i have to manually move it. If i don't do this, i can see the disected packets as shown in the image.
However, ATT packets received were showing UnknownDirection error as shown in the image. If you have any idea about it, please me know.
Finally, coming to the ticket ble-sniffer-osx(v1.2.4) app crashes continously on my Mac Book Pro (v10.11.6 El Capitan). I'm able to open the app 1 out 10. I have attached the crash report.
UnknownDirection is a wireshark issue - the current BTLE plugin removes direction information before decoding the encapsulated packet, I don't know why, it looks like a bug, I wasn't able to get any information from the people who support it as to why they did this when direction information is supplied at the top level. I don't see any way in which any full BTLE packet decode can possibly end up with direction information at the LE layer because the direction is removed before the dissection. Older versions of Wireshark didn't do that.
If you have to move the plugin then it seems you have a non-standard installation/configuration, ~/.wireshark/plugins is the standard location for plugins (that is documented somewhere) so I'm not sure why you are pointing to .config/.. it shouldn't really matter, but the code only looks in the standard place. Perhaps a re-install of the release Wireshark might help, or perhaps you have an old config file it's reading.
You didn't actually append the crashlog. My guess is it's another issue coming from the USB changes in OSX 10.11, there were quite a few issues although I've fixed all the ones I found so far, the USB system in OSX 10.11 was pretty much rewritten and I had some timing issues when devices were attached and enumerated. It also works really badly with the adafruit dongle which often the USB subsystem doesn't even recognise, I assume because that dongle uses the FTDI chip for USB and the Segger ones use Atmel and they seem to have fewer issues. Please append the crashlog although I'm off on vacation in .. 2 hours until mid August and so it probably won't get looked at for a while, I'm not taking any nordic dongles with me.