Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: [Wireshark-dev] ERROR "Duplicate protocol name"

From: Alex Lindberg <alindber@xxxxxxxxx>
Date: Fri, 1 Jun 2012 14:30:15 -0700 (PDT)
Build just before SVN update today was fine., however now after update this PM (01June) builds OK, but failure when running ./tshark -v.

$ svn info
Path: .
URL: http://anonsvn.wireshark.org/wireshark/trunk
Repository Root: http://anonsvn.wireshark.org/wireshark
Repository UUID: f5534014-38df-0310-8fa8-9805f1628bb7
Revision: 42990
Node Kind: directory
Schedule: normal
Last Changed Author: gerald
Last Changed Rev: 42990
Last Changed Date: 2012-06-01 15:54:04 -0500 (Fri, 01 Jun 2012)

Builds OK, however when running ./tshark -v the following error is generated:
   Duplicate protocol name "Coseventcomm Dissector Using GIOP API"

A backtrace of the stack shows:
libtool --mode=execute gdb ./tshark
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/rse/DEV/Wireshark.org/trunk/.libs/lt-tshark...done.
(gdb) r
Starting program: /home/rse/DEV/Wireshark.org/trunk/.libs/lt-tshark 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".

** (process:9695): ERROR **: Duplicate protocol name "Coseventcomm Dissector Using GIOP API"! This might be caused by an inappropriate plugin or a development error.

Program received signal SIGTRAP, Trace/breakpoint trap.
g_logv (log_domain=log_domain@entry=0x0, log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
    format=format@entry=0xb696d130 "Duplicate protocol name \"%s\"! This might be caused by an inappropriate plugin or a development error.", 
    args1=args1@entry=0xbffff09c "\360S7\264 \260\067\264") at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmessages.c:765
765     /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmessages.c: No such file or directory.
(gdb) bt
#0  g_logv (log_domain=log_domain@entry=0x0, log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
    format=format@entry=0xb696d130 "Duplicate protocol name \"%s\"! This might be caused by an inappropriate plugin or a development error.", 
    args1=args1@entry=0xbffff09c "\360S7\264 \260\067\264") at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmessages.c:765
#1  0xb55190c3 in g_log (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR, 
    format=0xb696d130 "Duplicate protocol name \"%s\"! This might be caused by an inappropriate plugin or a development error.")
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmessages.c:792
#2  0xb5be5a2a in proto_register_protocol (name=0xb43753f0 "Coseventcomm Dissector Using GIOP API", short_name=0xb4375314 "COSEVENTCOMM", filter_name=0xb43753c9 "giop-coseventcomm")
    at proto.c:4433
#3  0xb4375161 in proto_register_giop_coseventcomm () at packet-coseventcomm.c:729
#4  0xb4375295 in plugin_register () at packet-coseventcomm.c:778
#5  0xb5bd2c79 in register_all_plugin_registrations () at plugins.c:437
#6  0xb5be62da in proto_init (register_all_protocols_func=0x8050690 <register_all_protocols@plt>, register_all_handoffs_func=0x8050ec0 <register_all_protocol_handoffs@plt>, cb=0, 
    client_data=0x0) at proto.c:394
#7  0xb5bc5361 in epan_init (register_all_protocols_func=0x8050690 <register_all_protocols@plt>, register_all_handoffs_func=0x8050ec0 <register_all_protocol_handoffs@plt>, cb=0, 
    client_data=0x0, report_failure_fcn_p=0x80605b0 <failure_message>, report_open_failure_fcn_p=0x8060630 <open_failure_message>, 
    report_read_failure_fcn_p=0x8062630 <read_failure_message>, report_write_failure_fcn_p=0x8062600 <write_failure_message>) at epan.c:113
#8  0x08052399 in main (argc=1, argv=0xbffff6f4) at tshark.c:955
(gdb)