Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: gdb@sourceware.org
Subject: Re: generic error with a statically linked multithreaded program
Date: Thu, 05 Apr 2007 10:51:00 -0000	[thread overview]
Message-ID: <20070405.195148.45520318.nemoto@toshiba-tops.co.jp> (raw)
In-Reply-To: <20070405.145806.89068923.nemoto@toshiba-tops.co.jp>

On Thu, 05 Apr 2007 14:58:06 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
> I found gdb can not run a statically linked multithreaded program on
> Fedora Core 6.

And here is an output with debug lin-lwp.

(gdb) set debug lin-lwp 1
(gdb) run
Starting program: ./hello 
LLW: waitpid 12681 received Trace/breakpoint trap (stopped)
LLW: Candidate event Trace/breakpoint trap (stopped) in process 12681.
LLTA: PTRACE_PEEKUSER process 12681, 0, 0 (OK)
LLW: trap_ptid is process 12681.
LLR: Preparing to resume process -1, 0, inferior_ptid process -1
LLR: PTRACE_CONT process 12681, 0 (resume event thread)
LLW: waitpid 12681 received Trace/breakpoint trap (stopped)
LLW: Candidate event Trace/breakpoint trap (stopped) in process 12681.
LLTA: PTRACE_PEEKUSER process 12681, 0, 0 (OK)
LLW: trap_ptid is process 12681.
[Thread debugging using libthread_db enabled]
Cannot find new threads: generic error
(gdb) quit
The program is running.  Exit anyway? (y or n) y
KC:  PTRACE_KILL process 12681, 0, 0 (OK)
KWC: wait process 12681 received unk.

Then gdb hangs.

---
Atsushi Nemoto


  reply	other threads:[~2007-04-05 10:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05  5:58 Atsushi Nemoto
2007-04-05 10:51 ` Atsushi Nemoto [this message]
2007-04-05 14:29 ` Daniel Jacobowitz
2007-04-05 14:39   ` Atsushi Nemoto
2007-04-05 14:45     ` Daniel Jacobowitz
2007-04-06  9:40       ` Atsushi Nemoto
2007-04-19  9:19         ` Atsushi Nemoto

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=20070405.195148.45520318.nemoto@toshiba-tops.co.jp \
    --to=anemo@mba.ocn.ne.jp \
    --cc=gdb@sourceware.org \
    /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