From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8285 invoked by alias); 10 Oct 2002 15:56:32 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 8258 invoked from network); 10 Oct 2002 15:56:31 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 10 Oct 2002 15:56:31 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g9AFaZX05182 for ; Thu, 10 Oct 2002 11:36:35 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g9AFuTf01568; Thu, 10 Oct 2002 11:56:29 -0400 Received: from valrhona.uglyboxes.com (IDENT:5vdqJbnGb6JzZNDpzunMGDHgVZQrLA+V@vpn50-14.rdu.redhat.com [172.16.50.14]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g9AFuSa04432; Thu, 10 Oct 2002 11:56:28 -0400 Date: Thu, 10 Oct 2002 08:56:00 -0000 From: Keith Seitz X-X-Sender: keiths@valrhona.uglyboxes.com To: Masahide Tomita cc: insight@sources.redhat.com Subject: Re: Can threaded program be remotely debugged using Insight ? In-Reply-To: <002c01c26ffa$67f60a00$41dc280a@ABKNEECBCPCD65> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-q4/txt/msg00027.txt.bz2 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