--- Comment #5 from rguenth at gcc dot gnu dot org 2008-08-01 20:15 ---
Well, that only hints at that the bss section is not cleared properly which
is the job of the kernel and/or the dynamic linker.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37001
--- Comment #4 from gerald at wireshark dot org 2008-08-01 19:05 ---
I am "the application developer" and I've done my job. I'm asking you why gcc
isn't setting a variable to 0 when we've explicitly told it to do so.
Watching tap_current gives me the following:
GNU gdb 6.6-debian
Copyri
--- Comment #3 from rguenth at gcc dot gnu dot org 2008-08-01 17:24 ---
Just as a hint - as this is a static symbol you may want to use a gdb
watchpoint to see what changes it. Just do
gdb> watch tap_current
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37001
--- Comment #2 from rguenth at gcc dot gnu dot org 2008-08-01 17:23 ---
GCC 4.1 is no longer maintained, please try a newer version and provide a
smaller testcase (we are _not_ downloading software and debugging it - this
is the obligation of the application developer).
--
http://gc
--- Comment #1 from gerald at wireshark dot org 2008-08-01 16:31 ---
Created an attachment (id=15993)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15993&action=view)
Add debugging printfs to epan/dissectors/packet-gsm_a.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37001
