Bug#174027: glibc: another backtrace
On Tue, Dec 24, 2002 at 12:41:09PM -0500, Daniel Jacobowitz <dan@debian.org> wrote:
> This appears to be a different problem from the original one in this bug
> report. If it still happens with -8 (forthcoming) please file another
> report.
It does, will file another report.
> I have the feeling it has to do with your change or rebuild, because
> catchp involves the thread-specific data extensions...
No, it happens the same with the "official" 2.3.1-7. The reason I used a
rebuild is that a glibc built for 2.2 will always segfault in these perl
programs (although only at a later stage), so I needed to make sure it's
not _this_, already well understood, problem ;)
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
Reply to: