Hello!
When I run the program "bug" [1] under valgrind, I get a lot of error
messages [2]. Is it really a bug in glibc or is it a Valgrind bug?
Thanks,
Jakson
[1] The program "bug"
#include
#include
#include
int main(){
char *s = NULL;
struc
Processing commands for [EMAIL PROTECTED]:
> reassign 324051 libc6.1-dev
Bug#324051: Bogus free space display on Alpha
Bug#329870: pydf: Does not start on alpha architecture after installing
Bug reassigned from package `python2.3' to `libc6.1-dev'.
> retitle 324051 bad struct statvfs declaration
Accepted:
libc6-dbg_2.3.5-8_s390.deb
to pool/main/g/glibc/libc6-dbg_2.3.5-8_s390.deb
libc6-dev-s390x_2.3.5-8_s390.deb
to pool/main/g/glibc/libc6-dev-s390x_2.3.5-8_s390.deb
libc6-dev_2.3.5-8_s390.deb
to pool/main/g/glibc/libc6-dev_2.3.5-8_s390.deb
libc6-pic_2.3.5-8_s390.deb
to pool/main/g/g
On Sun, Nov 13, 2005 at 08:29:56PM +0100, Bastian Blank wrote:
> On Sun, Nov 13, 2005 at 02:04:45PM -0500, Daniel Jacobowitz wrote:
> > On Sun, Nov 13, 2005 at 07:30:47PM +0100, Bastian Blank wrote:
> > > On Sun, Nov 13, 2005 at 12:44:40PM -0500, Daniel Jacobowitz wrote:
> > > > What kernel is the
On Sun, Nov 13, 2005 at 02:04:45PM -0500, Daniel Jacobowitz wrote:
> On Sun, Nov 13, 2005 at 07:30:47PM +0100, Bastian Blank wrote:
> > On Sun, Nov 13, 2005 at 12:44:40PM -0500, Daniel Jacobowitz wrote:
> > > What kernel is the build daemon running? Does it have threading
> > > problems? I don't
glibc_2.3.5-8_s390.changes uploaded successfully to localhost
along with the files:
libc6_2.3.5-8_s390.deb
libc6-dev_2.3.5-8_s390.deb
libc6-prof_2.3.5-8_s390.deb
libc6-pic_2.3.5-8_s390.deb
libc6-s390x_2.3.5-8_s390.deb
libc6-dev-s390x_2.3.5-8_s390.deb
nscd_2.3.5-8_s390.deb
libc6-dbg_
On Sun, Nov 13, 2005 at 07:30:47PM +0100, Bastian Blank wrote:
> On Sun, Nov 13, 2005 at 12:44:40PM -0500, Daniel Jacobowitz wrote:
> > What kernel is the build daemon running? Does it have threading
> > problems? I don't think glibc 2.3.5 has ever successfully autobuilt on
> > s390.
>
> It was
On Sun, Nov 13, 2005 at 12:44:40PM -0500, Daniel Jacobowitz wrote:
> What kernel is the build daemon running? Does it have threading
> problems? I don't think glibc 2.3.5 has ever successfully autobuilt on
> s390.
It was built on debian01 which runs 2.6.11.
Bastian
--
Youth doesn't excuse eve
If you take a look at the build log for 2.3.5-8:
http://buildd.debian.org/fetch.php?&pkg=glibc&ver=2.3.5-8&arch=s390&stamp=1131871464&file=log&as=raw
you'll see that it timed out. This is almost certainly caused by the
terrible NPTL test results; some of them leave background processes
running i
Uwe Schindler wrote:
Another simple program that creates defunct processes is
gnome-cups-manager and also mysql creates them. Since I run a testing
system with a replaced libpthread.so (the one Tom created) and setted
libc6.1 to "HOLD", there are no more defunct processes and no other
problems
Another simple program that creates defunct processes is
gnome-cups-manager and also mysql creates them. Since I run a testing
system with a replaced libpthread.so (the one Tom created) and setted
libc6.1 to "HOLD", there are no more defunct processes and no other
problems occur.
Could it be
11 matches
Mail list logo