From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Received: (qmail 23235 invoked from network); 20 May 2004 18:05:12 -0000 Received: from unknown (HELO fed1rmmtao09.cox.net) (68.230.241.30) by sourceware.org with SMTP; 20 May 2004 18:05:12 -0000 Received: from ip68-3-5-250.ph.ph.cox.net ([68.3.5.250]) by fed1rmmtao09.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20040520180452.SZCJ22459.fed1rmmtao09.cox.net@ip68-3-5-250.ph.ph.cox.net> for ; Thu, 20 May 2004 14:04:52 -0400 Received: (qmail 6028 invoked from network); 20 May 2004 18:04:51 -0000 Received: from localhost (HELO cox.net) (127.0.0.1) by ip68-3-5-250.ph.ph.cox.net with SMTP; 20 May 2004 18:04:51 -0000 Message-ID: <40ACF33D.3020502@cox.net> Date: Thu, 20 May 2004 18:05:00 -0000 From: "Stephen P. Smith" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: Kevin Buettner CC: gdb Subject: Re: shared library support References: <20040517120219.5fad9bc0@saguaro> <40AA1198.2010808@cox.net> <20040518084422.5f94d1d5@saguaro> <40AA4328.6000109@cox.net> <20040518114817.76d0632d@saguaro> In-Reply-To: <20040518114817.76d0632d@saguaro> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00138.txt.bz2 ./gdb/solib-svr4.c warning ("no shared library support for this OS / ABI"); Sorry about misleading you. sps Kevin Buettner wrote: >On Tue, 18 May 2004 10:08:56 -0700 >"Stephen P. Smith" wrote: > > > >>Kevin Buettner wrote: >> >> >> >>>Where, precisely, is that message coming from? >>> >>> >>I don't know where it is coming from. I am using the insight tree, but >>I have verified that the GDB code has been mucked with. The source was >>fetched on the 14th from CVS. >> >> > >Would you mind searching for the error message in your source tree? I >looked for the message you quoted earlier today in a set of up-to-date >gdb sources, but came up empty. > >You might also try placing a breakpoint on error() or warning() to >find out where this message is being generated. > >Kevin > > > >