Wireshark-dev: Re: [Wireshark-dev] Bug in register.c generation
From: Joerg Mayer <[email protected]>
Date: Sat, 14 Apr 2007 01:42:24 +0200
On Fri, Apr 13, 2007 at 04:05:05PM -0700, Gerald Combs wrote:
> > I've got a problem with the generation of the register.c file:
> > 
> > [email protected]:~/work/wireshark/trunk/epan/dissectors> sort register.c | uniq -c | grep -v " 1 "
> >       2
> >       2 {
> >       2 }
> >       2   {extern void proto_register_cisco_oui (void); proto_register_cisco_oui ();}
> >       2 void
> > 
> > that block is in there twice. No idea why, it's only once in the cache file.
> 
> Are you looking at the strings in the cache file or dumping it out, e.g.
> with
> 
>   import pickle, pprint
>   pprint.pprint(pickle.load(open('epan/dissectors/register-cache.pkl')))

Just looked at the file - I'm afraid I'm completely illiterate when I
comes to reading python files.

> ?  I can't find anything that might cause duplicates in
> make-dissector-reg.py, but it probably wouldn't hurt to check for
> duplicates before we write out the lists of routines.

And the even more interesting thing is: Why didn't it happen right from
the start but started only about 2 days ago?
I'll investigate further, using the test above.

 Thanks
     Joerg

-- 
Joerg Mayer                                           <[email protected]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.