[Roland Knall <rknall@xxxxxxxxx>]

I think, there should be some rules, as to what an extcap interface is supposed to be able to do and what not. Basically in this case, the device simply writes to stdout, no matter what.

I do think, that it should not output anything, if called with --extcap-interfaces. 

regards,

Roland

On Thu, Apr 30, 2015 at 10:08 PM, Guy Harris <guy@xxxxxxxxxxxx> wrote:

On Apr 30, 2015, at 1:00 PM, Roland Knall <rknall@xxxxxxxxx> wrote:

> On Thu, Apr 30, 2015 at 6:58 PM, Joerg Mayer <jmayer@xxxxxxxxx> wrote:
> ERROR: Cannot connect to ADB: Connection refused
> INFO: Please check that adb daemon is running.
>
> Do not know about the others, but
> "ERROR: Cannot connect to ADB: Connection refused
> INFO: Please check that adb daemon is running."
>
> is the new androiddump extcap utility, and I think it should be ok, that this message is printed, as it is an external tool, not Wireshark itself.

Is it run whenever you start Wireshark, even if you don't have any Android development tools installed?

If not, is it still run even if you don't happen to be debugging an Android device at the time?

It should perhaps try to distinguish, if possible, between "failure to connect to ADB when you're actually debugging an Android device" and "failure to connect to ADB because {you're not using any Android development tools right now, you don't even have Android development tools installed, you don't have any Android devices on which to develop, etc.}".

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe