From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21087 invoked by alias); 22 Nov 2008 12:00:40 -0000 Received: (qmail 21035 invoked by uid 22791); 22 Nov 2008 12:00:39 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout5.012.net.il (HELO mtaout5.012.net.il) (84.95.2.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 22 Nov 2008 11:59:41 +0000 Received: from conversion-daemon.i_mtaout5.012.net.il by i_mtaout5.012.net.il (HyperSendmail v2004.12) id <0KAQ00J00H9W2800@i_mtaout5.012.net.il> for gdb-patches@sourceware.org; Sat, 22 Nov 2008 14:01:07 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.126.14.29]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KAQ000COHDBSL81@i_mtaout5.012.net.il>; Sat, 22 Nov 2008 14:01:07 +0200 (IST) Date: Sat, 22 Nov 2008 21:41:00 -0000 From: Eli Zaretskii Subject: Re: too many "no debugging symbols found" messages from shared libs In-reply-to: X-012-Sender: halo1@inter.net.il To: Doug Evans Cc: mark.kettenis@xs4all.nl, brobecker@adacore.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: References: <18261.86.86.3.213.1227305211.squirrel@webmail.xs4all.nl> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-11/txt/msg00606.txt.bz2 > Date: Fri, 21 Nov 2008 14:53:39 -0800 > From: Doug Evans > Cc: Eli Zaretskii , brobecker@adacore.com, > gdb-patches@sourceware.org > > The outstanding question is: When debugging executables with symbols, > do we want to start printing "no debugging symbols found" messages for > every such shared library encountered as the default behavior? If > yes, it can still be turned off with "set print symbol-loading off". > If no, then the user would have to turn on some other option in order > to see them ("set verbose on" is the current proposal). > > Comments? I agree that the current logic has its flaws, but I think I understand the difficulty: the problem is with shared libraries that are part of the program you are debugging vs system libraries, like libc.so. We probably do NOT want to hear about stripped system libraries by default, but we do want those messages for libraries that are part of the application, if the application isn't stripped. Can we find a good way of supporting both these use cases?