Package: gdb
Version: 6.3-5
Severity: normal

I'm not sure what is wrong, but often when I try to debug a program that
uses threads, I cannot get a proper backtrace. Instead, I get something
like this (the example is from gst-compprep-0.8):

  Program received signal SIGILL, Illegal instruction.
  0x0f08de24 in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  (gdb) where
  #0  0x0f08de24 in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #1  0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #2  0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #3  0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #4  0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #5  0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #6  0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #7  0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #8  0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #9  0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #10 0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #11 0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  #12 0x0f08dd4c in mpeg2_detect_accel () from /usr/lib/libmpeg2.so.0
  Previous frame inner to this frame (corrupt stack?)
  (gdb)

I don't know what other information to give, bug feel free to ask, of
course.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-powerpc
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages gdb depends on:
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libncurses5                 5.4-4        Shared libraries for terminal hand
ii  libreadline4                4.3-15       GNU readline and history libraries

-- no debconf information


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

Reply via email to