Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Michael Snyder <msnyder@vmware.com>,
	        "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] Fix for gdb.threads/staticthreads.exp failure on Linux
Date: Thu, 16 Jul 2009 02:43:00 -0000	[thread overview]
Message-ID: <e394668d0907151929v1a260d7ga1d9b406d5bed48e@mail.gmail.com> (raw)
In-Reply-To: <e394668d0907151825t12283c66rc1856a242d50332a@mail.gmail.com>

On Wed, Jul 15, 2009 at 6:25 PM, Doug Evans<dje@google.com> wrote:
> Running the testcase with --target_board=native-gdbserver doesn't have
> this problem.  Some research as to what gdbserver is doing would be
> illuminating.  "consistency is good": can you research what's
> happening in gdbserver that it works there, and see if it's reasonable
> to do the same thing in gdb?

I spoke too soon.  gdbserver does have the same problem, I just needed
to look at gdb.log to see it.

Process /usr/local/g3/gnu/sourceware/static-threads/build/obj32/gdb/testsuite/gdb.threads/staticthreads
created; pid = 19691^M
Listening on port 2347^M
target remote localhost:2347^M
Remote debugging using localhost:2347^M
Remote debugging from host 127.0.0.1^M
Cannot get thread handle for LWP 19691: generic error^M
_start () at ../sysdeps/i386/elf/start.S:65^M
65              xorl %ebp, %ebp^M
(gdb) Cannot get thread handle for LWP 19691: generic error^M
continue^M
Continuing.^M
^M
Breakpoint 1, main (argc=<value optimized out>, argv=<value optimized
out>) at ../../../../src/gdb/testsuite/gdb.threads/staticthreads.c:51^M
51        pthread_attr_init (&attr);^M
Current language:  auto; currently c^M
(gdb) PASS: gdb.threads/staticthreads.exp: rerun to main

[The "value optimized out" seems like a bug, but a different bug. :-)]


  reply	other threads:[~2009-07-16  2:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 22:22 Paul Pluzhnikov
2009-06-15 18:39 ` Paul Pluzhnikov
2009-06-22 16:10   ` Paul Pluzhnikov
2009-06-22 18:10     ` Michael Snyder
2009-06-22 20:21       ` Paul Pluzhnikov
2009-06-29 14:36         ` Paul Pluzhnikov
2009-07-09  6:36           ` Paul Pluzhnikov
2009-07-16  2:42         ` Doug Evans
2009-07-16  2:43           ` Doug Evans [this message]
2009-07-16 20:45           ` Paul Pluzhnikov
2009-07-16 20:54             ` Paul Pluzhnikov
2009-07-16 21:16             ` Doug Evans

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=e394668d0907151929v1a260d7ga1d9b406d5bed48e@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=ppluzhnikov@google.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