google / google/ios-webkit-debug-proxy
Segmentation fault if an action is taken from the developer tools while device is locked
Open
- Dominant language
- C
- Stars
- 6.2k
- Forks
- 480
- PR merge metrics
- No merged PRs in 30d
Description
The program immediately segfaults if you do the following process;
1. Connect device, start `ios_webkit_debug_proxy`
2. Open debugger to an open page
3. Lock the device or allow it to lock automatically
4. Attempt to use the debugger
Running on Ubuntu 13.04 with libplist 1.10, libusbmuxd 1.0.8 and libimobiledevice 1.1.5.
I get the impression from the readme that `ios_webkit_debug_proxy` should be able to start with no devices attached, and survive disconnections and reconnections. Neither appear to be the case in the environment I'm using it in.
Contributor guide
Assessment
This issue has not been assessed yet.