A starting point for this is now on gerrit:
https://code.wireshark.org/review/#/c/965/
It does all the tvb_get_* routines, but only the proto_add_* routine for
guint8. I didn't bother creating the other variants for that routine because
there are open questions in it still.
It already helped
On Apr 4, 2014, at 2:01 PM, Hadriel Kaplan hadriel.kap...@oracle.com wrote:
For protocols which are actually truly UTF-8, I'm planning to just assume
treating them as ASCII is ok, because as far as I know the atoi/strtol/etc.
functions don't actually care: if they see the ASCII characters
Many thanks! Fix was committed in https://code.wireshark.org/review/#/c/971/
(Still not sure of the why it failed , but I'll gladly take this solution)
-Original Message-
From: Hadriel Kaplan hadriel.kap...@oracle.com
To: Developer support list for Wireshark
2014-04-04 19:03 GMT+02:00 Gerald Combs ger...@wireshark.org:
I'd like to upgrade our 32-bit Windows buildbot from XP to 8.1 in the
near future. Aside from the obvious EOL issue it's difficult to use
automated management and packaging tools like Puppet and Chocolatey
under XP. Upgrading would
On Apr 4, 2014, at 4:04 PM, Guy Harris g...@alum.mit.edu wrote:
Likewise, it’s not clear if there’s a way to define a protocol field that is
encoded as a string in the packet but is internally a uint8/16/32/64 (e.g.,
for filtering purposes, val_string lookup, etc.). For example such that
Khemis Haythem
Adresse : Boite Postale 101 4118, Mednine
GSM : +216 55 69 19 90
E-mail : khemis.hayt...@yahoo.fr
Statut : Élève ingénieur
Spatialité : Génie des Communications et des Réseaux
Ecole : Ecole National d'Ingénieurs de Gabes
hello
i m trying to build envirenement
here i do
