This is the mail archive of the
mailing list for the glibc project.
[Bug libc/695] New: Glibc issue??
- From: "giffordj at linkline dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 25 Jan 2005 23:28:29 -0000
- Subject: [Bug libc/695] New: Glibc issue??
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
I have 2 indentical boxes. Cobalt RaQ2's. The only difference in them is the
toolchain. All boxes are using Gcc 3.4.3 and Bintuils 188.8.131.52.1, the
difference is the glibc. One is using the 11-22-2004 and the other is using
Here is the issue compiling procps 3.2.4 on both boxes no errors, but when ran
on the 01-03-2005 snapshot I get the following error message.
PID TTY TIME CMD
0 ? 00:00:01 init
Signal 11 (SEGV) caught by ps (procps version 3.2.4).
Please send bug reports to <email@example.com> or <firstname.lastname@example.org>
Now if I copy ps from the machine that has the 11-22-2004 snapshot of glibc and
run it on the box with the 01-03-2005 it runs with no issues at all.
Is this a glibc issue or procps? In the next entry I will be attaching an strace
log for this, I know you probably would like a gdb output, put gdb doesn't work
it gives me some wierd error message on any version about breakpoints.
Summary: Glibc issue??
AssignedTo: gotom at debian dot or dot jp
ReportedBy: giffordj at linkline dot com
CC: glibc-bugs at sources dot redhat dot com
GCC host triplet: mipsel-unknown-linux-gnu
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.