public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Cal Erickson <cal_erickson@mvista.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Masahide Tomita <fsi_tomi@bcpc601.neec.abk.nec.co.jp>,
	insight@sources.redhat.com
Subject: Re: Can threaded program be remotely debugged using Insight ?
Date: Thu, 10 Oct 2002 09:05:00 -0000	[thread overview]
Message-ID: <3DA5A39F.4060600@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210100856350.1958-100000@valrhona.uglyboxes.com>

Current versions of gdbserver are incapable of debugging threaded 
programs. They do not have enough knowledge of how threads are set up 
and used. There are projects which are trying to remedy this. An 
interesting feature in the 5.2 and later versions of gdbserver is the 
ability to attach to a running process. However make note of the fact 
that I used the word process and not thread.

Cal Erickson

Keith Seitz wrote:

> On Thu, 10 Oct 2002, Masahide Tomita wrote:
> 
> 
>>Thank you for the reply.
>>Anyway, how come mail from you everytime arrive twice?
>>
> 
> If you're subscribed to the mailing list, you'd get my reply via that 
> route as well as from me directly.
> 
> 
>>I locally run gdb (not Insight) on target, to see if this is target oriented
>>issue, and I get thread created and program going, but I get the message
>>below now:
>>
>>Program received signal SIG32, Real-time event 32.
>>0x4005db75 in sigsuspend( ) from /lib/libc.so.6
>>
> 
> Ok, this is definitely a gdb or gdbserver issue, then. This subject seems 
> vaguely familiar: I've seen this discussed recently somewhere. I would 
> recommend sending a gdb session showing the error to 
> gdb@sources.redhat.com, where the gdb experts hang out.
> 
> Keith
> 
> 
> 
> 


-- 
===========================================================================
Cal Erickson                 MontaVista Software Inc.
Linux Consultant             1237 E. Arques Ave.
Phone (408) 328-0304         Sunnyvale CA 94085
Fax   (408) 328-9204         web http://www.mvista.com
===========================================================================

      reply	other threads:[~2002-10-10 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09  7:30 Masahide Tomita
2002-10-09  8:02 ` Keith Seitz
2002-10-09 18:14   ` Masahide Tomita
2002-10-10  8:56     ` Keith Seitz
2002-10-10  9:05       ` Cal Erickson [this message]

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=3DA5A39F.4060600@mvista.com \
    --to=cal_erickson@mvista.com \
    --cc=fsi_tomi@bcpc601.neec.abk.nec.co.jp \
    --cc=insight@sources.redhat.com \
    --cc=keiths@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).