From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <archer-return-1677-listarch-archer=sourceware.org@sourceware.org>
Received: (qmail 26151 invoked by alias); 23 Sep 2009 14:08:39 -0000
Mailing-List: contact archer-help@sourceware.org; run by ezmlm
Sender: <archer@sourceware.org>
Precedence: bulk
List-Post: <mailto:archer@sourceware.org>
List-Help: <mailto:archer-help@sourceware.org>
List-Subscribe: <mailto:archer-subscribe@sourceware.org>
List-Id: <archer.sourceware.org>
Received: (qmail 26136 invoked by uid 22791); 23 Sep 2009 14:08:38 -0000
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0
	tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
From: Dragos Tatulea <dragos.tatulea@gmail.com>
Date: Wed, 23 Sep 2009 14:08:00 -0000
Message-ID: <6d1764b50909230708l60a4be26ocf3bf6aef198710@mail.gmail.com>
Subject: Re: [Keith Seitz] Re: [tools-team] Status 2008-09-01
To: keiths@redhat.com
Cc: archer@sourceware.org, jan.kratochvil@redhat.com, cmoller@redhat.com
Content-Type: text/plain; charset=ISO-8859-1
X-SW-Source: 2009-q3/txt/msg00243.txt.bz2

Hi Keith,

> That is, I think "set print object on" ought to affect the type of the
> resulting history variable -- but not the type of any intermediate
> values in an expression.
>
> Jan> One should change this (+some other related options in
> Jan> `user_print_options') and in some way fix the testsuite regressions
> Jan> afterwards by one of:
>
> I agree, we should change this default.

I changed objectprint to on by default on Jan's suggestion, but this breaks some
other cases like this one (from ptr-typedef test)

struct foo {
  int x;
};

typedef struct foo *foz;

int
main (void)
{
  foz_ptr = NULL;
}

gdb> p foz_ptr
$1 = (struct foo *) 0x0
instead of
(foz*)

So the change isn't acceptable.

Back to the previous case: Jan suggested printing an error/warning for the user
saying that the ptr has a different type (and maybe printing the type). What do
you think?

Thanks,
Dragos