From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20043 invoked by alias); 23 Jan 2008 16:16:00 -0000 Received: (qmail 20035 invoked by uid 22791); 23 Jan 2008 16:15:59 -0000 X-Spam-Check-By: sourceware.org Received: from mail.suse.de (HELO mx1.suse.de) (195.135.220.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 23 Jan 2008 16:15:40 +0000 Received: from Relay1.suse.de (mail2.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.suse.de (Postfix) with ESMTP id 99CD627010 for ; Wed, 23 Jan 2008 17:15:37 +0100 (CET) Date: Wed, 23 Jan 2008 16:16:00 -0000 From: Olaf Hering To: gdb@sourceware.org Subject: gdb follows symlinks when looking for debuginfo Message-ID: <20080123161537.GA25123@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-DOS: I got your 640K Real Mode Right Here Buddy! X-Homeland-Security: You are not supposed to read this line! You are a terrorist! User-Agent: Mutt und vi sind doch schneller als Notes (und GroupWise) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00231.txt.bz2 Why does gdb follow symlinks when looking for debuginfo and executables? The binaries in our installation images are symlinked into a loop-mounted cramfs image, or to an extracted tree on a remote filesystem. The gdb binary itself is a symlink /usr/bin/gdb -> /mounts/inst-sys/usr/bin/gdb. For some reason, gdb starts to look for debuginfo in /mounts/inst-sys/usr/lib/debug instead of just /usr/lib/debug. The same is true for the executable thats being debugged. How can this be turned off? I do not see a cmdline switch for that.