From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7004 invoked by alias); 18 Jul 2005 16:01:21 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6783 invoked by uid 22791); 18 Jul 2005 16:01:02 -0000 Received: from web52013.mail.yahoo.com (HELO web52013.mail.yahoo.com) (206.190.48.96) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Mon, 18 Jul 2005 16:01:02 +0000 Received: (qmail 37753 invoked by uid 60001); 18 Jul 2005 16:01:00 -0000 Message-ID: <20050718160100.37751.qmail@web52013.mail.yahoo.com> Received: from [192.160.144.253] by web52013.mail.yahoo.com via HTTP; Mon, 18 Jul 2005 09:01:00 PDT X-RocketYMMF: natkelcri Date: Mon, 18 Jul 2005 16:01:00 -0000 From: Larry Martell Reply-To: larry@software-horizons.com Subject: Re: gdb runs multi-threaded with non-threaded app and gets SEGV To: gdb@sources.redhat.com In-Reply-To: <20050716005207.16238.qmail@web52001.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-SW-Source: 2005-07/txt/msg00190.txt.bz2 --- Larry Martell wrote: > --- "Min Xu (Hsu)" wrote: > > On Fri, 15 Jul 2005 Larry Martell wrote : > > > --- "Min Xu (Hsu)" wrote: > > > > > > > Larry, > > > > > > > > How about you run the program and let the > > program > > > > pass the > > > > lib call without using GDB. And spin there > until > > gdb > > > > is attached? > > > > > > I tried this, but after it attaches to the > > process, > > > as then I try to continue it, it immediatly gets > > > a SEGV. And it sounded like such a good idea too > > :-( > > > > How can this be possible is beyond me. :-( > > > > Are yo using SPARC? > > No, I'm on a P4 running Linux. My app makes many > calls > to functions from this lib. It seems a call to any > one of them causes the SEGV from within gdb. Like I > said before, it doesn't do this when I run it > outside > of gdb, but it worries me. (I had forgotten how much > fun it is debugging with printf's ;-) I just got an email from the third party lib vendor (National Instruments): > We have found incompatibilities with GDB, valgrind, > and the NI-488.2 driver. This will be fixed in the > next version of our driver. So I guess I'm sol wrt gdb until they fix this lib :-( Thanks to all who here who replied and tried to help. -larry