https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15454
--- Comment #9 from Maksim Salau <maksim.sa...@gmail.com> ---
Hi Guy
(In reply to Guy Harris from comment #8)
> Either Flex & Bison/BYACC (if there's any .y file in the Wireshark source
> that works only with Bison, not Berkeley YACC, that's a bug), or Flex &
> Lemon (most of the generated parsers in Wireshark are Lemon, not
> Bison/BYACC).
Please elaborate on byacc compatibility.
I've implemented the parser with flex & bison. Just a parser, no integration
into wireshark dissector yet. I've chosen bison, since I'm new to describing
parser syntax and help with bison is easier available to me :)
I tried byacc and it works fine with valid input. But if I induce errors I get
memory leaks, since byacc shipped with Fedora doesn't have support for btyacc
extensions and thus I'm not allowed to use %destructor directive to get rid of
memory allocated data.
So here is the question: does Wireshark require btyacc extensions to be
enabled?
Here is what I get:
$ byacc -L
byacc: w - -L flag unsupported, reconfigure with --enable-btyacc
Since lemon parser generator looks more predictable across platforms for
obvious reasons, I consider rewriting parser using lemon, if there will be no
way ensure btyacc extensions presence.
Regards,
Maksim
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
