[Wireshark-dev] Rappel : Can't start 2.5: Err Duplicate protocol name "DOCSIS Vendor Specific Encodings"

2018-02-20 Thread RobiOneKenobi 
RobiOneKenobi souhaite rappeler le message « [Wireshark-dev] Can't start
2.5: Err Duplicate protocol name"DOCSIS Vendor Specific
Encodings" ».
<>___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Can't start 2.5: Err Duplicate protocol name "DOCSIS Vendor Specific Encodings"

2018-02-20 Thread RobiOneKenobi 
Hi,

Yes, you can probably remove an old plugin dll with this name (in the plugin 
directory where your exe is build and stared)

Robert

-Original Message-
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of 
david_agge...@hispeed.ch
Sent: Tuesday, February 20, 2018 4:46 PM
To: 'Developer support list for Wireshark' 
Subject: [Wireshark-dev] Can't start 2.5: Err Duplicate protocol name "DOCSIS 
Vendor Specific Encodings"


I'm trying to build & run 2.5. After I pulled the latest code last Friday I 
can't start it anymore. I get:
 
"Err  Duplicate protocol name "DOCSIS Vendor Specific Encodings"! This might be 
caused by an inappropriate plugin or a development error. Press any key to exit"

On the same machine I build and run 2.2 & 2.4 successfully.

So I pull code again today, did the prepare und build, and it is still the 
same. I tried with empty %AppData%\wireshark as well. 
I did not try to 'remove' the DOCSIS from the supported dissectors. 

Any advice?

Regards
David



___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] gerrit registration problems

2018-02-20 Thread Richard Sharpe 
On Tue, Feb 20, 2018 at 7:07 PM, Ed Beroset  wrote:
> On 01/31/2018 09:44 AM, Ed Beroset wrote:
>>
>> I've submitted code to Wireshark in the past, but not since Gerrit.  I
>> tried again yesterday to register and now I remember why it's been so long
>> -- I can't seem to register.  Is this the place to ask for help, or is there
>> a better way to do it?
>
>
> I may or may not be registered and I may or may not have submitted a patch.
> I followed the instructions here:
> https://www.wireshark.org/docs/wsdg_html_chunked/ChSrcContribute.html
>
> Git seems to have accepted the push, but I don't see any evidence that it
> exists when I go to https://code.wireshark.org/review/#/dashboard/self
>
> Any troubleshooting clues, or is it normal that a successful push has no
> observable manifestation?

Is it this one?

https://code.wireshark.org/review/#/c/25956/

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] gerrit registration problems

2018-02-20 Thread Ed Beroset 

On 01/31/2018 09:44 AM, Ed Beroset wrote:
I've submitted code to Wireshark in the past, but not since Gerrit.  I 
tried again yesterday to register and now I remember why it's been so 
long -- I can't seem to register.  Is this the place to ask for help, or 
is there a better way to do it?


I may or may not be registered and I may or may not have submitted a 
patch.  I followed the instructions here: 
https://www.wireshark.org/docs/wsdg_html_chunked/ChSrcContribute.html


Git seems to have accepted the push, but I don't see any evidence that 
it exists when I go to https://code.wireshark.org/review/#/dashboard/self


Any troubleshooting clues, or is it normal that a successful push has no 
observable manifestation?


Ed
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Windows builds seem to fail with some frequency even though the Linux builds don't!

2018-02-20 Thread Richard Sharpe 
Hi,

I have noticed over the last few days that Windows builds are failing
quite a lot even though the Linux builds are not.

Also, I cannot seem to find the reason for the build failures.

Is it something I am doing?

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Problem with background dumpcap in Windows

2018-02-20 Thread Craig Jackson 
Running on recent builds on Windows, I've had a problem with dumpcap being
started and exiting repeatedly in the background. This seems to happening
when it's being restarted to update the interface statistics, such as
happens after a capture file is closed. The interface statistics update
just fine before opening a capture file.

My assumption is that this has something to do with my environment,
although I've blown away my build directory and rebuilt several times. I've
also rebased regularly against master. However, I don't know enough Windows
debugging to figure out what's going wrong.

I was able to see it happening with Procmon from Sysinternals. Should I
install Sysmon from Sysinternals to capture more information? How would I
get dumpcap to run under the debugger.

Craig Jackson
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Can't start 2.5: Err Duplicate protocol name "DOCSIS Vendor Specific Encodings"

2018-02-20 Thread david_aggeler 
 

Thanks. That solved it.

 

Regards

David

 

From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of 
Anders Broman
Sent: Tuesday, February 20, 2018 4:49 PM
To: Developer support list for Wireshark 
Subject: Re: [Wireshark-dev] Can't start 2.5: Err Duplicate protocol name 
"DOCSIS Vendor Specific Encodings"

 

The docsis dissector was moved from a plugin to a built in dissector. You 
probably have the old docsis plugin executable left in your plugin directory. 
Delete it.

Regards 

Anders 

 

Den 20 feb. 2018 4:45 em skrev mailto:david_agge...@hispeed.ch> >:


I'm trying to build & run 2.5. After I pulled the latest code last Friday I 
can't start it anymore. I get:

"Err  Duplicate protocol name "DOCSIS Vendor Specific Encodings"! This might be 
caused by an inappropriate plugin or a development error. Press any key to exit"

On the same machine I build and run 2.2 & 2.4 successfully.

So I pull code again today, did the prepare und build, and it is still the 
same. I tried with empty %AppData%\wireshark as well.
I did not try to 'remove' the DOCSIS from the supported dissectors.

Any advice?

Regards
David



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

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Can't start 2.5: Err Duplicate protocol name "DOCSIS Vendor Specific Encodings"

2018-02-20 Thread Anders Broman 
The docsis dissector was moved from a plugin to a built in dissector. You
probably have the old docsis plugin executable left in your plugin
directory. Delete it.
Regards
Anders

Den 20 feb. 2018 4:45 em skrev :

>
> I'm trying to build & run 2.5. After I pulled the latest code last Friday
> I can't start it anymore. I get:
>
> "Err  Duplicate protocol name "DOCSIS Vendor Specific Encodings"! This
> might be caused by an inappropriate plugin or a development error. Press
> any key to exit"
>
> On the same machine I build and run 2.2 & 2.4 successfully.
>
> So I pull code again today, did the prepare und build, and it is still the
> same. I tried with empty %AppData%\wireshark as well.
> I did not try to 'remove' the DOCSIS from the supported dissectors.
>
> Any advice?
>
> Regards
> David
>
>
>
> 
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=
> unsubscribe
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Can't start 2.5: Err Duplicate protocol name "DOCSIS Vendor Specific Encodings"

2018-02-20 Thread david_aggeler 

I'm trying to build & run 2.5. After I pulled the latest code last Friday I 
can't start it anymore. I get:
 
"Err  Duplicate protocol name "DOCSIS Vendor Specific Encodings"! This might be 
caused by an inappropriate plugin or a development error. Press any key to exit"

On the same machine I build and run 2.2 & 2.4 successfully.

So I pull code again today, did the prepare und build, and it is still the 
same. I tried with empty %AppData%\wireshark as well. 
I did not try to 'remove' the DOCSIS from the supported dissectors. 

Any advice?

Regards
David



___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe