From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: gdb@sources.redhat.com
Subject: Re: gdbserver: thread getmsg err on mips[el]-linux
Date: Wed, 09 Feb 2005 14:55:00 -0000 [thread overview]
Message-ID: <20050209.235331.102580003.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <20050114.174802.55486536.nemoto@toshiba-tops.co.jp>
>>>>> On Fri, 14 Jan 2005 17:48:02 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> said:
anemo> Hi. When I tried to debug multi thread program with gdbserver
anemo> (6.3.50_20050104) on mips[el]-linux, I got following error:
anemo> [[gdbserver side]]
anemo> ...
anemo> thread getmsg err: no event message for getmsg
anemo> Segmentation fault
I finally see what's wrong. This is not gdb's fault but kernel's.
The fix is now in linux-mips CVS.
http://www.linux-mips.org/archives/linux-mips/2005-02/msg00103.html
http://www.linux-mips.org/archives/linux-cvs-patches/2005-02/msg00041.html
---
Atsushi Nemoto
next prev parent reply other threads:[~2005-02-09 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 8:48 Atsushi Nemoto
2005-01-28 10:43 ` Atsushi Nemoto
2005-02-09 14:55 ` Atsushi Nemoto [this message]
2005-02-09 14:57 ` Daniel Jacobowitz
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=20050209.235331.102580003.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--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