From: [email protected]

Package: file
Version: 4.10-3
Severity: serious

Noticed during gcc builds, that the calls to `file' during the gcc
build (i.e. calls to dh_strip) need too much memory, 'file' eating up to
1GB of RAM. I didn't see this behaviour on other architectures.



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

Martin Michlmayr writes:

* Matthias Klose <[email protected]> [2004-08-11 00:12]:

Noticed during gcc builds, that the calls to `file' during the gcc
build (i.e. calls to dh_strip) need too much memory, 'file' eating
up to 1GB of RAM. I didn't see this behaviour on other
architectures.

Did file change recently? Did you try with another version. Do you
still have that gcc binary so this bug can be reproduced?

to reproduce on your host:

- su to doko
- chroot unstable ...
- cd gcc-3.3-3.3.4
- rm stamps/07* stamps/08*
- fakeroot debian/rules binary-arch


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

* Matthias Klose <[email protected]> [2004-08-11 00:12]:

Noticed during gcc builds, that the calls to `file' during the gcc
build (i.e. calls to dh_strip) need too much memory, 'file' eating
up to 1GB of RAM. I didn't see this behaviour on other
architectures.

Did file change recently? Did you try with another version. Do you
still have that gcc binary so this bug can be reproduced?
--
Martin Michlmayr
[email protected]


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

If I'm not totally mistaken, this looks like a fakeroot problem to me.
I can run "file cpp-3.3" just fine, but "fakeroot file cpp-3.3"
segfaults (and works on i386). During "fakeroot debian/rules

arch-specific fakeroot problems seem to mean that fakeroot is
exposing a kernel or libc bug.

What version of fakeroot?

Does it segfault under gdb (see instructions in
/usr/share/doc/fakeroot/DEBUG)? If so, is the backtrace useful?

kill(24046, SIGTERM) = 0
SYS_4246( <unfinished ... exit status 139>

What's 4246 on mips?


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

* Clint Adams <[email protected]> [2004-08-12 13:33]:

arch-specific fakeroot problems seem to mean that fakeroot is
exposing a kernel or libc bug.

Hmm, it might be that the chroot is fucked. I just copied the binary
to another chroot and "fakeroot file" worked. Both are up-to-date
unstable chroots, though.
--
Martin Michlmayr
[email protected]


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

* Matthias Klose <[email protected]> [2004-08-13 11:41]:

not reproducible in a fresh chroot.

Hmm, I just generated anoter chroot and see it... I'll check some
things, and maybe give Clint access if that would help.
--
Martin Michlmayr
[email protected]


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)