Closed HenryHoggard closed 10 years ago
This crashes on scanner.provider.sqltables too,
We lost your drozer session.
For some reason the mobile Agent has stopped responding. You will need to restart it, and try again.
We lost your drozer session.
For some reason the mobile Agent has stopped responding. You will need to restart it, and try again.
[Errno 32] Broken pipe
Can you please post any logcat output around the time of the crash.
Also, which version of Android are you using?
From: Henry [mailto:notifications@github.com] Sent: Thursday, August 01, 2013 01:25 PM To: mwrlabs/drozer drozer@noreply.github.com Subject: Re: [drozer] Crash on scanner.provider.traversal (#86)
This crashes on scanner.provider.sqltables too,
We lost your drozer session.
For some reason the mobile Agent has stopped responding. You will need to restart it, and try again.
We lost your drozer session.
For some reason the mobile Agent has stopped responding. You will need to restart it, and try again.
[Errno 32] Broken pipe
— Reply to this email directly or view it on GitHubhttps://github.com/mwrlabs/drozer/issues/86#issuecomment-21932626.
@dbradberry The logcat is included in the issue, but I do not think you can see it in the email update you got. It starts just before the crash and I stopped it about 4 seconds after the crash. The emulator is 4.0.0.
楼主有没有解决问题的方法啊
@anjingweixiao 我已經更新了最新的版本,新版本運作正常
@HenryHoggard 你好,我用的2.3.4 运行所有scanner方法都会crash 失去连接。请问你用的是哪个版本呢,有什么相关解决办法吗
you can use adb kill-server,then using adb start-server, adb forward tcp:31415 tcp:31415 and drozer console connect
EDIT
Fixed path errors, still crashes. Running Android 4.0.0 emulator
Every time I run scanner.provider.traversal it crashes on the very last app to scan. I have tried other modules which work fine however this crashes without fail.
I then cannot connect to the agent so I have to restart drozer server. I have added dx to the path and it still seems to error.
Drozer Log
ADB Logcat