After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 479602 - Firestarter firewall crashes with segfault if "Active Connections" drop down box is opened
Firestarter firewall crashes with segfault if "Active Connections" drop down ...
Status: RESOLVED WONTFIX
Product: firestarter
Classification: Deprecated
Component: general
unspecified
Other All
: Normal critical
: ---
Assigned To: Tomas Junnonen
Tomas Junnonen
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2007-09-23 18:52 UTC by Craig A. Eddy
Modified: 2011-12-06 06:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Craig A. Eddy 2007-09-23 18:52:49 UTC
Steps to reproduce:
1. Start firewall (may be set to autostart on startup, or manually through terminal).
2. When firewall window opens, click on "Active Connections" drop down arrow
3. Within about 10 minutes, Firestarter crashes out.


Stack trace:
Report from Valgrind, run on Firestarter:
+++++++++++++++++++++++++++++++++++++++++++
==7768== Memcheck, a memory error detector.
==7768== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==7768== Using LibVEX rev 1732, a library for dynamic binary translation.
==7768== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==7768== Using valgrind-3.2.3-Debian, a dynamic binary instrumentation framework.
==7768== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==7768== 
==7768== My PID = 7768, parent PID = 7750.  Prog and args are:
==7768==    firestarter
==7768== 
--7768-- 
--7768-- Command line
--7768--    firestarter
--7768-- Startup, with flags:
--7768--    -v
--7768--    --tool=memcheck
--7768--    --leak-check=full
--7768--    --num-callers=40
--7768--    --log-file=valgrind.log
--7768-- Contents of /proc/version:
--7768--   Linux version 2.6.22-12-generic (buildd@crested) (gcc version 4.1.3 20070831 (prerelease) (Ubuntu 4.1.2-16ubuntu1)) #1 SMP Sat Sep 22 17:45:57 GMT 2007
--7768-- Arch and hwcaps: AMD64, amd64-sse2
--7768-- Page sizes: currently 4096, max supported 4096
--7768-- Valgrind library directory: /usr/lib/valgrind
--7768-- Reading syms from /usr/sbin/firestarter (0x400000)
--7768-- Reading debug info from /usr/sbin/firestarter...
--7768-- ... CRC mismatch (computed 75D1ECEC wanted CF6D607D)
--7768--    object doesn't have a symbol table
--7768-- Reading syms from /lib/ld-2.6.1.so (0x4000000)
--7768-- Reading debug info from /lib/ld-2.6.1.so...
--7768-- ... CRC mismatch (computed F18656F0 wanted 247B0180)
--7768--    object doesn't have a symbol table
--7768-- Reading syms from /usr/lib/valgrind/amd64-linux/memcheck (0x38000000)
--7768--    object doesn't have a dynamic symbol table
--7768-- Reading suppressions file: /usr/lib/valgrind/default.supp
vex amd64->IR: unhandled instruction bytes: 0x66 0x66 0x66 0x66
==7768== valgrind: Unrecognised instruction at address 0x4016321.
==7768== Your program just tried to execute an instruction that Valgrind
==7768== did not recognise.  There are two possible reasons for this.
==7768== 1. Your program has a bug and erroneously jumped to a non-code
==7768==    location.  If you are running Memcheck and you just saw a
==7768==    warning about a bad jump, it's probably your program's fault.
==7768== 2. The instruction is legitimate but Valgrind doesn't handle it,
==7768==    i.e. it's Valgrind's fault.  If you think this is the case or
==7768==    you are not sure, please let us know and we'll try to fix it.
==7768== Either way, Valgrind will now raise a SIGILL signal which will
==7768== probably kill your program.
==7768== 
==7768== Process terminating with default action of signal 4 (SIGILL)
==7768==  Illegal opcode at address 0x4016321
==7768==    at 0x4016321: (within /lib/ld-2.6.1.so)
==7768==    by 0x400466E: (within /lib/ld-2.6.1.so)
==7768==    by 0x4014457: (within /lib/ld-2.6.1.so)
==7768==    by 0x400230A: (within /lib/ld-2.6.1.so)
==7768==    by 0x4000A67: (within /lib/ld-2.6.1.so)
==7768== 
==7768== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
--7768-- 
--7768-- supp:    1 dl-hack3
==7768== malloc/free: in use at exit: 0 bytes in 0 blocks.
==7768== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==7768== 
==7768== All heap blocks were freed -- no leaks are possible.
--7768--  memcheck: sanity checks: 0 cheap, 1 expensive
--7768--  memcheck: auxmaps: 0 auxmap entries (0k, 0M) in use
--7768--  memcheck: auxmaps: 0 searches, 0 comparisons
--7768--  memcheck: SMs: n_issued      = 7 (112k, 0M)
--7768--  memcheck: SMs: n_deissued    = 0 (0k, 0M)
--7768--  memcheck: SMs: max_noaccess  = 524287 (8388592k, 8191M)
--7768--  memcheck: SMs: max_undefined = 0 (0k, 0M)
--7768--  memcheck: SMs: max_defined   = 8 (128k, 0M)
--7768--  memcheck: SMs: max_non_DSM   = 7 (112k, 0M)
--7768--  memcheck: max sec V bit nodes:    0 (0k, 0M)
--7768--  memcheck: set_sec_vbits8 calls: 0 (new: 0, updates: 0)
--7768--  memcheck: max shadow mem size:   4256k, 4M
--7768-- translate:            fast SP updates identified: 175 ( 88.8%)
--7768-- translate:   generic_known SP updates identified: 13 (  6.5%)
--7768-- translate: generic_unknown SP updates identified: 9 (  4.5%)
--7768--     tt/tc: 800 tt lookups requiring 799 probes
--7768--     tt/tc: 800 fast-cache updates, 2 flushes
--7768--  transtab: new        400 (8,794 -> 151,036; ratio 171:10) [0 scs]
--7768--  transtab: dumped     0 (0 -> ??)
--7768--  transtab: discarded  0 (0 -> ??)
--7768-- scheduler: 1,154 jumps (bb entries).
--7768-- scheduler: 0/406 major/minor sched events.
--7768--    sanity: 1 cheap, 1 expensive checks.
--7768--    exectx: 30,011 lists, 1 contexts (avg 0 per list)
--7768--    exectx: 1 searches, 0 full compares (0 per 1000)
--7768--    exectx: 0 cmp2, 0 cmp4, 0 cmpAll
+++++++++++++++++++++++++++++++++++++++++++++++++
End Report

Other information:
Comment 1 Jean-François Fortin Tam 2008-02-05 03:25:58 UTC
I can confirm this.
Comment 2 Akhil Laddha 2011-12-06 06:15:54 UTC
firestarter development has been stalled and it has been unmaintained for a few years now. I contacted Tomas Junnonen (majix@iki.fi) because he is listed as Developer on project page but didn't get any response. I found firestarter on fedora wiki [1] under deprecated packages so i am closing all the bugs as WONTFIX. Please feel free to reopen the bugs in future if anyone takes the responsibility for active development.

[1] http://fedoraproject.org/wiki/Deprecated_packages