From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28083 invoked by alias); 13 Jul 2005 10:35:05 -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 28041 invoked from network); 13 Jul 2005 10:34:57 -0000 Received: from unknown (202.80.33.51) by sourceware.org with QMTP; 13 Jul 2005 10:34:57 -0000 Received: (qmail 5545 invoked from network); 13 Jul 2005 10:34:55 -0000 X-Anti-Virus: Message scanned for viruses by TVL Received: from du-248.vanuatu.com.vu (HELO sakuraindustries.com) ([202.80.40.248]) (envelope-sender ) by mail.vanuatu.com.vu (qmail-ldap-1.03) with SMTP for ; 13 Jul 2005 10:34:14 -0000 Message-ID: <42D62354.5090607@sakuraindustries.com> Date: Wed, 13 Jul 2005 10:35:00 -0000 From: Steven Johnson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.6) Gecko/20040115 MIME-Version: 1.0 To: Jonathan Larmour CC: Daniel Jacobowitz , gdb@sources.redhat.com Subject: Re: Thread backtrace termination References: <42D29C67.4070509@eCosCentric.com> <20050711162326.GA32686@nevyn.them.org> <42D2B1CD.2020605@eCosCentric.com> <20050711181907.GA4551@nevyn.them.org> <42D40C9D.7070204@eCosCentric.com> In-Reply-To: <42D40C9D.7070204@eCosCentric.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-07/txt/msg00144.txt.bz2 Jonathan Larmour wrote: > Daniel Jacobowitz wrote: > >> On Mon, Jul 11, 2005 at 06:52:13PM +0100, Jonathan Larmour wrote: >> >>> Daniel Jacobowitz wrote: >> [snip] >>> Alternatively, how about adding a new command that allows you to >>> define a set of entry point symbol names? People can then put an >>> appropriate list for themselves or their OS in ~/.gdbinit. Or it can >>> be pre-initialised by the OS support within GDB if there is one. >>> e.g. nm-linux.h. Here's what I'm thinking of: >>> >>> set entry-point-name-list main _start _entry >>> >>> Although handling mangled symbols and multiple languages might be >>> fun. I'm not an expert on such things. >> >> >> >> *shrug* maybe. > > > Well, I'm prepared to create a patch to add such a command if people > here think something with that principle would be accepted. Instead of a "set" command, which sets an entire list, an "add" and "delete" command that adds to the list and deletes from the list respectively would be (in my opinion) more useful, because GDB could default to the standard entries for a target, and then extra's could be added to/removed from the list. set entry-point-list add [name] set entry-point-list delete [name] (for example) Alternatively there could be 2 lists, one full of default which you usually dont change, and one with user added entries. set entry-point-name-list-default [list] set entry-point-name-list-user [list] By default user would be empty, and would be only set by the user (in a script or otherwise). So the user could be assured they werent messing with any defaults they didnt want to change. or the like. supporting wildcards might also be useful, such as: set entry-point-list add thread_* or set entry-point-list delete * so if a programmer had a convention of calling all their threads "thread_blah" they wouldnt have to explicitly name them all, back trace would terminate at any function with that naming convention. Just some suggestions, if you are going to do this. My opinion is such a feature would be worthwhile. If the information can not be easily provided (or at all) from debug symbols, it would seem highly desirable to have a manual method of inserting the information. Steven