public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: David Carlton <carlton@math.stanford.edu>, gdb@sources.redhat.com
Subject: Re: testsuite errors on Red Hat 8.0
Date: Wed, 16 Apr 2003 14:29:00 -0000	[thread overview]
Message-ID: <20030416142906.GB9574@nevyn.them.org> (raw)
In-Reply-To: <16029.26634.39200.540933@localhost.redhat.com>

On Wed, Apr 16, 2003 at 10:26:18AM -0400, Elena Zannoni wrote:
> Daniel Jacobowitz writes:
>  > On Tue, Apr 15, 2003 at 09:27:32PM -0700, David Carlton wrote:
>  > > On Wed, 16 Apr 2003 00:11:46 -0400, Daniel Jacobowitz <drow@mvista.com> said:
>  > > 
>  > > >> and in gdb.threads/pthreads.exp, I get:
>  > > >> 
>  > > >> FAIL: gdb.threads/pthreads.exp: check backtrace from main thread
>  > > >> FAIL: gdb.threads/pthreads.exp: apply backtrace command to all three threads
>  > > 
>  > > > These I'd definitely like to see the log for.
>  > > 
>  > > I'll put it after my signature.
>  > 
>  > 
>  > > thread apply 1 backtrace
>  > > 
>  > > Thread 1 (Thread 16384 (LWP 14967)):
>  > > #0  0x4013a816 in nanosleep () from /lib/libc.so.6
>  > > #1  0x00000000 in ?? ()
>  > > 51        if (verbose) printf("common_routine (%d)\n", arg);
>  > > (gdb) FAIL: gdb.threads/pthreads.exp: check backtrace from main thread
>  > 
>  > We can no longer backtrace out of nanosleep on your system, if we ever
>  > could.
>  > 
>  > The possible fixes:
>  >   - adding unwind info to glibc syscall stubs and making gdb use it
>  >   - synthesizing unwind info when we recognize a syscall stub and using
>  >     it
>  >   - improving the prologue analyzer until it works for this function
> 
> 
> he he he...See my posting about how bad this problem is going to bite
> us for NPTL kernels. About this particual problem, RH 8.0 doesn't have
> NPTL, but there could be some other interesting kernel 'feature' going
> on.

Fortunately, IIRC, Ulrich has added unwind info to glibc for syscall
wrappers in glibc now?  Next step is to use it!

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-04-16 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16  4:06 David Carlton
2003-04-16  4:11 ` Daniel Jacobowitz
2003-04-16  4:27   ` David Carlton
2003-04-16 13:34     ` Daniel Jacobowitz
2003-04-16 14:21       ` Elena Zannoni
2003-04-16 14:29         ` Daniel Jacobowitz [this message]
2003-04-16 14:23   ` Elena Zannoni
2003-04-16 16:21     ` David Carlton
2003-04-16 19:06       ` Elena Zannoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030416142906.GB9574@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).