[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 89106] the 'impossible' happened
From:       Jason LaVoie <lavoie () us ! ibm ! com>
Date:       2004-09-13 14:53:03
Message-ID: 20040913145303.16006.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

http://bugs.kde.org/show_bug.cgi?id‰106




------- Additional Comments From lavoie us ibm com  2004-09-13 16:52 -------
Oddly enough, the first run with num-callers  worked (I realize there should be no \
correlation between the two). Subsequent runs resulted in:

=765== Memcheck, a memory error detector for x86-linux.
=765== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward et al.
=765== Using valgrind-2.2.0, a program supervision framework for x86-linux.
=765== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al.
=765== For more details, rerun with: -v
=765==765== Syscall param sigaction(act) contains uninitialised or unaddressable \
byte(s) =765==    at 0x1B90F8D4: rt_sigaction (pth_rtsig.c:41)
=765==  Address 0x1BA6C164 is on thread 1's stack
--16765-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
--16765-- si_code=1 Fault EIP: 0xB002EA8D; Faulting address: 0x52BFCFC0

valgrind: the `impossible' happened:
   Killed by fatal signal
Basic block ctr is approximately 0
=765==    at 0xB002A3DA: vgPlain_core_panic (vg_mylibc.c:1156)
=765==    by 0xB002A3D9: panic (vg_mylibc.c:1152)
=765==    by 0xB002A3EE: vgPlain_core_panic (vg_mylibc.c:1157)
=765==    by 0xB0030627: vg_sync_signalhandler (vg_signals.c:2191)
=765==    by 0xB0043A19: (within /usr/local/lib/valgrind/stage2)

sched status:

Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
=765==    at 0x1B9FD6C6: read (in /lib/libc-2.3.2.so)
=765==    by 0x1B994F42: _IO_file_underflow  GLIBC_2 1 (in /lib/libc-2.3.2.so)
=765==    by 0x1B99762C: _IO_default_uflow_internal (in /lib/libc-2.3.2.so)
=765==    by 0x1B9972DC: __GI___uflow (in /lib/libc-2.3.2.so)
=765==    by 0x1B98B9F7: _IO_getline_info_internal (in /lib/libc-2.3.2.so)
=765==    by 0x1B98B8F2: _IO_getline_internal (in /lib/libc-2.3.2.so)
=765==    by 0x1B98A8EF: _IO_fgets (in /lib/libc-2.3.2.so)
=765==    by 0x8055E94: ParseConf (main.c:312)
=765==    by 0x805376D: user_init (socketcall.c:191)
=765==    by 0x804CF25: main (thttpd.c:264)


Line 312 of ParseConf is "return -1". The function parses a configuration file. \
Without Valgrind, everything executes fine (except for the memory leaks).

Thanks.


[prev in list] [next in list] [prev in thread] [next in thread]