From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4075 invoked by alias); 8 Nov 2002 23:02:53 -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 4064 invoked from network); 8 Nov 2002 23:02:53 -0000 Received: from unknown (HELO hermes.wildseed.com) (66.239.226.123) by sources.redhat.com with SMTP; 8 Nov 2002 23:02:53 -0000 Received: (qmail 5156 invoked from network); 8 Nov 2002 22:58:26 -0000 Received: from unknown (HELO neptune.kirkland.local) (66.239.226.125) by 0 with SMTP; 8 Nov 2002 22:58:26 -0000 Received: by neptune.kirkland.local with Internet Mail Service (5.5.2653.19) id ; Fri, 8 Nov 2002 15:02:51 -0800 Message-ID: <43CB1396676FD4119F03001083FD299401547970@neptune.kirkland.local> From: "Kevin \"Sharpie\" Endres" To: gdb@sources.redhat.com Subject: Question about resolving symbol information from so's loaded via dlopen. Date: Fri, 08 Nov 2002 15:02:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2002-11/txt/msg00092.txt.bz2 in GDB 5.2.1. I am attempting to debug using a core from an application that loads an .so via dlopen using an absolute location. When i target the core in gdb - the .so's attempt to load using the absolute path (the core file was not generated on my machine) and fail. How do I work around this? Thanks in advance. :]k