The following list of warnings are worth taking a look at:
Might this cause problems on older compilers?
ftype-double.c:69:48: warning: use of C99 hexadecimal floating constant
This message first appeared when compiling with -O3 (instead of -O2). Does this
ring a bell somewhere?
packet.c:392: warning: variable `saved_proto' might be clobbered by `longjmp' or `vfork'
packet.c:393: warning: variable `saved_can_desegment' might be clobbered by `longjmp' or `vfork'
packet-eth.c:164: warning: variable `ehdr' might be clobbered by `longjmp' or `vfork'
packet-eth.c:167: warning: variable `src_addr' might be clobbered by `longjmp' or `vfork'
packet-eth.c:167: warning: variable `dst_addr' might be clobbered by `longjmp' or `vfork'
packet-ethertype.c:150: warning: variable `next_tvb' might be clobbered by `longjmp' or `vfork'
packet-ethertype.c:151: warning: variable `length_before' might be clobbered by `longjmp' or `vfork'
packet-ethertype.c:153: warning: variable `saved_proto' might be clobbered by `longjmp' or `vfork'
packet-ldp.c:2126: warning: variable `next_tvb' might be clobbered by `longjmp' or `vfork'
packet-sflow.c:329: warning: variable `next_tvb' might be clobbered by `longjmp' or `vfork'
packet-sflow.c:330: warning: variable `sflow_header_tree' might be clobbered by `longjmp' or `vfork'
packet-sflow.c:334: warning: variable `save_writable' might be clobbered by `longjmp' or `vfork'
packet-tcp.c:1889: warning: variable `next_tvb' might be clobbered by `longjmp' or `vfork'
packet-tds.c:1067: warning: variable `next_tvb' might be clobbered by `longjmp' or `vfork'
packet-tr.c:328: warning: variable `frame_type' might be clobbered by `longjmp' or `vfork'
packet-tr.c:343: warning: variable `trh' might be clobbered by `longjmp' or `vfork'
packet-vlan.c:70: warning: variable `encap_proto' might be clobbered by `longjmp' or `vfork'
packet-x11.c:3101: warning: variable `next_tvb' might be clobbered by `longjmp' or `vfork'
Value stored in guint8 is always smaller than 256 (changed but not fixed):
ansi_map_stat.c:103: warning: comparison is always false due to limited range of data type
isup_stat.c:104: warning: comparison is always false due to limited range of data type
Ciao
Jörg
--
Joerg Mayer <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
