Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Leutwein Tobias (BEG-PT/ESB1)" <Tobias.Leutwein@de.bosch.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: AW: [RFC, patch] ptype bitfields show bitpos and bitsize
Date: Thu, 26 Jan 2012 10:15:00 -0000	[thread overview]
Message-ID: <1606F039DD6642449BF6D1519D43AF62161994A2A6@SI-MBX09.de.bosch.com> (raw)
In-Reply-To: <20120125112233.GA18042@host2.jankratochvil.net>

After running the testsuite I saw that

(gdb) ptype int

returns
Attempt to use a type name as an expression

instead of
type = int

The change at eval.c leads to this change of the behaviour.

So I have to make some changes to the patch. If it's possible, I also want to move the content of the c_type_print_base_through_value function to the c_type_print_base function.

I think end of next week I will have the changes.


> -----Ursprüngliche Nachricht-----
> Von: Jan Kratochvil [mailto:jan.kratochvil@redhat.com]
> Gesendet: Mittwoch, 25. Januar 2012 12:23
> An: Leutwein Tobias (BEG-PT/ESB1)
> Cc: gdb-patches@sourceware.org
> Betreff: Re: [RFC, patch] ptype bitfields show bitpos and bitsize
>
> On Wed, 25 Jan 2012 12:17:48 +0100, Leutwein Tobias (BEG-PT/ESB1)
> wrote:
> > I have made some changes to the GDB sources to get more information's
> about
> > bitfield variables through the ptype command.
>
> That's great.  Just please read gdb/CONTRIBUTE, missing at least FSF
> ChangeLog
> and such change also needs to be convered in gdb/testsuite/.
>
>
> Thanks,
> Jan


  reply	other threads:[~2012-01-26  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 11:22 Leutwein Tobias (BEG-PT/ESB1)
2012-01-25 14:16 ` Jan Kratochvil
2012-01-26 10:15   ` Leutwein Tobias (BEG-PT/ESB1) [this message]
2012-02-20 12:26   ` AW: " Leutwein Tobias (BEG-PT/ESB1)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1606F039DD6642449BF6D1519D43AF62161994A2A6@SI-MBX09.de.bosch.com \
    --to=tobias.leutwein@de.bosch.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox