Re: [Wireshark-dev] Wireshark runtime messages we don't want to see

2015-04-30 Thread Joerg Mayer
On Thu, Apr 30, 2015 at 01:44:41PM -0700, Guy Harris wrote: > On Apr 30, 2015, at 9:58 AM, Joerg Mayer wrote: > > > jmayer@egg epan$ wireshark > > ../../asn1/c1222/packet-c1222-template.c:1427:3: runtime error: null > > pointer passed as argument 1, which is declared to never be null > > ../../a

Re: [Wireshark-dev] Wireshark runtime messages we don't want to see

2015-04-30 Thread Joerg Mayer
On Thu, Apr 30, 2015 at 01:08:59PM -0700, Guy Harris wrote: > On Apr 30, 2015, at 1:00 PM, Roland Knall wrote: > > > On Thu, Apr 30, 2015 at 6:58 PM, Joerg Mayer wrote: > > ERROR: Cannot connect to ADB: Connection refused > > INFO: Please check that adb daemon is running. > > > > Do not know ab

Re: [Wireshark-dev] Wireshark runtime messages we don't want to see

2015-04-30 Thread Alexis La Goutte
On Thu, Apr 30, 2015 at 10:44 PM, Guy Harris wrote: > > On Apr 30, 2015, at 9:58 AM, Joerg Mayer wrote: > > > jmayer@egg epan$ wireshark > > QMetaObject::connectSlotsByName: No matching signal for > on_actionExternalMenuItem_triggered() > About this warning, i coming from eeed4d1121f122aa5579153

Re: [Wireshark-dev] Wireshark runtime messages we don't want to see

2015-04-30 Thread Guy Harris
On Apr 30, 2015, at 9:58 AM, Joerg Mayer wrote: > jmayer@egg epan$ wireshark > QMetaObject::connectSlotsByName: No matching signal for > on_actionExternalMenuItem_triggered() > ../../asn1/c1222/packet-c1222-template.c:1427:3: runtime error: null pointer > passed as argument 1, which is declare

Re: [Wireshark-dev] Wireshark runtime messages we don't want to see

2015-04-30 Thread Roland Knall
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, A

Re: [Wireshark-dev] Wireshark runtime messages we don't want to see

2015-04-30 Thread Guy Harris
On Apr 30, 2015, at 1:00 PM, Roland Knall wrote: > On Thu, Apr 30, 2015 at 6:58 PM, Joerg Mayer 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

Re: [Wireshark-dev] Wireshark runtime messages we don't want to see

2015-04-30 Thread Roland Knall
On Thu, Apr 30, 2015 at 6:58 PM, Joerg Mayer 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 ne

[Wireshark-dev] Wireshark runtime messages we don't want to see

2015-04-30 Thread Joerg Mayer
jmayer@egg epan$ wireshark QMetaObject::connectSlotsByName: No matching signal for on_actionExternalMenuItem_triggered() ../../asn1/c1222/packet-c1222-template.c:1427:3: runtime error: null pointer passed as argument 1, which is declared to never be null ../../asn1/c1222/packet-c1222-template.c:1