Bug#220584: upgrade to 2.3.2.ds1-10 makes everything linked to libpthread segfault

[Daniel Jacobowitz <dan@debian.org>]

On Thu, Nov 13, 2003 at 04:10:59PM +0100, Adrian von Bidder wrote:
Content-Description: signed data
> [sorry for the duplication - this should obviously go to bugs.d.o, too]
> [no more mail from me today]
> 
> On Thursday 13 November 2003 15:07, you wrote:
> > On Thu, Nov 13, 2003 at 02:43:32PM +0100, Adrian von Bidder wrote:
> > > doesn't work:
> > > $ cat /proc/cpuinfo
> > > processor       : 0
> > > vendor_id       : CentaurHauls
> > > cpu family      : 6
> > > model           : 7
> > > model name      : VIA Samuel 2
> > > stepping        : 3
> >
> > This is probably it.
> >
> > (A) Do you have libc6-i686 installed?
> 
> Nope. Installing it makes no difference, though.
> 
> > (B) What's the rest of the procinfo entry say?
> Sorry, assumed you'd know that cpu anyway
> 
> couscous:~# cat /proc/cpuinfo 
> processor       : 0
> vendor_id       : CentaurHauls
> cpu family      : 6
> model           : 7
> model name      : VIA Samuel 2
> stepping        : 3
> cpu MHz         : 533.357
> cache size      : 64 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu de tsc msr cx8 mtrr pge mmx 3dnow
> bogomips        : 1061.68

Ldd says that it's using the copy in /lib, right?

> > (C) Can you get gdb to show you where something is crashing?
> how do I do this - those program don't have debugging symbols, so a backtrace 
> won't work 'just so'. Sorry, I'm no gdb-geek...

Just send me the output of:
  info shared
  backtrace
  info registers
  x/10i $pc

Some of that should be useful.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer