Quickly determine where your duplicate ett_definition is ...

[Richard Sharpe <realrichardsharpe () gmail com>]

Hi folks,

I just had a nasty issue with duplicate ett_* entries (well, one, actually).

The issue was in dissector A but I was working on dissector B and had
not run Wireshark after building with the changes in A, so it looked
like the issue was in B.

I notice that proto_register_subtree_array does not take any
parameters indicating which dissector it is called from.

Could we make that call a macro that passes the code line and function
name as the last two parameters so the g_error printed out can tell us
where the problem lies?

In the end I used gdb to figure it out, but life would have been
easier if the error message told me.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe