On Mon, Jun 06, 2005 at 11:32:01PM -0400, Daniel Jacobowitz wrote:
> On Sun, Jun 05, 2005 at 12:15:42PM -0400, Daniel Jacobowitz wrote:
> > This will have nothing to do with threads. Probably that library is
> > compiled with -fomit-frame-pointer and does not include debugging
> > information; tha
On Sun, Jun 05, 2005 at 12:15:42PM -0400, Daniel Jacobowitz wrote:
> This will have nothing to do with threads. Probably that library is
> compiled with -fomit-frame-pointer and does not include debugging
> information; that means that GDB simply can't figure out the stack
> frame. The only way t
On Sun, Jun 05, 2005 at 09:42:12AM +0200, Matijs van Zuijlen wrote:
> 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
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.
4 matches
Mail list logo
