From: "Masahide Tomita" <fsi_tomi@bcpc601.neec.abk.nec.co.jp>
To: <insight@sources.redhat.com>
Cc: "Keith Seitz" <keiths@redhat.com>
Subject: Re: Can threaded program be remotely debugged using Insight ?
Date: Wed, 09 Oct 2002 18:14:00 -0000 [thread overview]
Message-ID: <002c01c26ffa$67f60a00$41dc280a@ABKNEECBCPCD65> (raw)
In-Reply-To: <Pine.LNX.4.44.0210090803400.1823-100000@valrhona.uglyboxes.com>
Hi Keith,
Thank you for the reply.
Anyway, how come mail from you everytime arrive twice?
> On Wed, 9 Oct 2002, Masahide Tomita wrote:
>
> > So, my real questions are:
> >
> > 1. Is this a problem of insight, or gdb?
>
> Can you run this with just GDB (gdb -nw)? It sounds like a gdb bug, but
> running "-nw" will tell us for sure.
I tried this one, and got same result, as long as I try to debug remotely.
Debugging locally goes more than just fine, even with GUI mode.
> > 2. Is there any way to debug threded program by using gdb, or insight?
>
> I think that the real problem may be the warning you saw, but we'll get to
> that after we determine whether Insight is at fault.
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
These, I don't get from gdb on PC.
GDB versions of both PC and target are same.
I can't even guess what the problem is now.
Somebody please help me.
Thank you.
--
Masahide Tomita
next prev parent reply other threads:[~2002-10-10 1:14 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 [this message]
2002-10-10 8:56 ` Keith Seitz
2002-10-10 9:05 ` Cal Erickson
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='002c01c26ffa$67f60a00$41dc280a@ABKNEECBCPCD65' \
--to=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).