Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Doug Evans <dje@sebabeach.org>, gdb-patches@sourceware.org
Subject: Re: [RFA] Ensure result of make_cleanup is never NULL.
Date: Mon, 16 Apr 2012 14:58:00 -0000	[thread overview]
Message-ID: <20120416145514.GA18963@host2.jankratochvil.net> (raw)
In-Reply-To: <20120416144011.GH2852@adacore.com>

On Mon, 16 Apr 2012 16:40:11 +0200, Joel Brobecker wrote:
> Just a tiny idea, not really important, but JIC: Could we use an enum
> intead of a define so that GDB prints "CLEANUP_FENCEPOST" rather than
> a numeric value when we print a cleanup pointer that's the fencepost?

It will not work, it is a pointer, not enum.

Maybe one could add something to gdb-gdb.py but it also did not work for me.


Jan


  reply	other threads:[~2012-04-16 14:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  5:01 Doug Evans
2012-04-16 10:58 ` Pedro Alves
2012-04-16 14:44 ` Joel Brobecker
2012-04-16 14:58   ` Jan Kratochvil [this message]
2012-04-16 15:03   ` Pedro Alves
2012-04-16 20:16     ` Tom Tromey
     [not found]     ` <CADPb22SfUk5s9JSSBvUTWVyhoiEqO4Gi+VNO-9MwH6rqW8qQ3g@mail.gmail.com>
2012-04-17 23:12       ` Doug Evans
2012-04-18  1:06         ` Doug Evans
2012-04-18  1:58           ` Joel Brobecker
2012-04-18  9:21             ` Pedro Alves
2012-04-18  9:29           ` Pedro Alves
2012-04-18 14:14             ` Doug Evans
2012-04-18 14:25               ` Pedro Alves
2012-04-18 14:32                 ` Doug Evans
2012-04-18 14:36                   ` Pedro Alves
2012-04-18 14:38                 ` Tom Tromey
2012-04-19 19:24                   ` Doug Evans
2012-04-18  9:26         ` Pedro Alves

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=20120416145514.GA18963@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=dje@sebabeach.org \
    --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