From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15036 invoked by alias); 6 Dec 2001 17:46:01 -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 14893 invoked from network); 6 Dec 2001 17:45:57 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 6 Dec 2001 17:45:57 -0000 Received: (from mec@localhost) by duracef.shout.net (8.8.7/8.8.7) id LAA12491; Thu, 6 Dec 2001 11:45:40 -0600 Date: Thu, 06 Dec 2001 09:46:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200112061745.LAA12491@duracef.shout.net> To: drow@mvista.com, gdb@sources.redhat.com Subject: Re: Handling of structure dereferencing X-SW-Source: 2001-12/txt/msg00056.txt.bz2 > So, straw poll: how would people feel about: > - not letting this happen; only explicit dereferencing As a user, this would be fine with me, although I can see how it would bother other users. It's 10x more important to me that "print foo.a" and "print foo.b()" never return incorrect data. I can live with virtual baseclass botch, but when the debugger prints an incorrect value, that destroys my faith in all the other values it prints. If getting rid of the implicit dereference helps, I'm all for it. Michael C