From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25190 invoked by alias); 18 Jul 2003 00:32:35 -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 25183 invoked from network); 18 Jul 2003 00:32:34 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by sources.redhat.com with SMTP; 18 Jul 2003 00:32:34 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19dJ9n-0003nH-00 for ; Fri, 18 Jul 2003 02:31:31 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gdb@sources.redhat.com Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19dJ9l-0003n6-00 for ; Fri, 18 Jul 2003 02:31:29 +0200 From: David Wuertele Subject: Re: cross-debugging with gdbserver, why can't gdb find breakpoint function? Date: Fri, 18 Jul 2003 00:32:00 -0000 Organization: Berkeley Fluent Network Message-ID: References: <200307171620.38131.jon.ringle@comdial.com> <20030717203016.GA28000@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@main.gmane.org User-Agent: Gnus/5.090018 (Oort Gnus v0.18) Emacs/21.2 (gnu/linux) Cancel-Lock: sha1:yWrtq1d3KVjMAI9FEtXNztOQpqw= X-SW-Source: 2003-07/txt/msg00229.txt.bz2 Daniel> Please, don't do it that way. For David's setup the right way Daniel> is: (gdb) set solib-absolute-prefix /nfsroot Thanks, this solved it for me. Daniel> If you can point to somewhere you looked in the documentation Daniel> and didn't see this, I'd love to improve it. The first place I looked was to google for the error message: "warning: Unable to find dynamic linker breakpoint function." This found a bunch of people who asked the same or a similar question, but no answers anything remotely like yours. My next step was to search for keywords in that error message in the info files. Didn't find anything there either. Then I tried READMEs. Then I tried this group. If there were a "troubleshooting" page in the manual that included error messages mapped to suggestions, it would have been simple. Thanks again, Dave