forked from osmocom/wireshark
AMQP 1.0: float/double should be in network byte order
The standard says that (unless otherwise specified) AMQP uses network byte order for all numeric values. Change-Id: I3ca154a6fb882d9194a9af891f92f760aae776eb Reviewed-on: https://code.wireshark.org/review/8889 Reviewed-by: Pascal Quantin <pascal.quantin@gmail.com>
This commit is contained in:
parent
74421b35c2
commit
7a927d60d4
|
@ -10927,7 +10927,7 @@ format_amqp_1_0_float(tvbuff_t *tvb,
|
|||
const char **value)
|
||||
{
|
||||
float floatval;
|
||||
floatval = tvb_get_letohieee_float(tvb, offset);
|
||||
floatval = tvb_get_ntohieee_float(tvb, offset);
|
||||
*value = wmem_strdup_printf(wmem_packet_scope(), "%f", floatval);
|
||||
return 4;
|
||||
}
|
||||
|
@ -10938,7 +10938,7 @@ format_amqp_1_0_double(tvbuff_t *tvb,
|
|||
const char **value)
|
||||
{
|
||||
double doubleval;
|
||||
doubleval = tvb_get_letohieee_double(tvb, offset);
|
||||
doubleval = tvb_get_ntohieee_double(tvb, offset);
|
||||
*value = wmem_strdup_printf(wmem_packet_scope(), "%f", doubleval);
|
||||
return 8;
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue