public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13483] gdb not taking 0 for pointer and boolean values
Date: Wed, 07 Dec 2011 20:19:00 -0000	[thread overview]
Message-ID: <bug-13483-4717-sadAu8rMyP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13483-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13483

--- Comment #2 from Diego Novillo <dnovillo at google dot com> 2011-12-07 20:18:45 UTC ---
On 12/07/11 15:14, keiths at redhat dot com wrote:
> http://sourceware.org/bugzilla/show_bug.cgi?id=13483
>
> Keith Seitz<keiths at redhat dot com>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |keiths at redhat dot com
>
> --- Comment #1 from Keith Seitz<keiths at redhat dot com>  2011-12-07 20:14:13 UTC ---
> What version of gdb? I checked in a patch for 13225 which should at least allow
> the pointer to work without a cast. I suspect "bool" needs similar treatment.
> Does just casting the bool work?


Sorry, forgot to include that.  We are using a slightly modified version 
of 7.3.1:

$ gdb --version
GNU gdb (GDB) 7.3.1

If I cast the bool argument, it works fine, yes.



Diego.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-12-07 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 19:36 [Bug gdb/13483] New: " dnovillo at google dot com
2011-12-07 20:15 ` [Bug gdb/13483] " keiths at redhat dot com
2011-12-07 20:19 ` dnovillo at google dot com [this message]
2012-09-10 17:13 ` cvs-commit at gcc dot gnu.org
2012-09-12 18:44 ` keiths at redhat dot com

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=bug-13483-4717-sadAu8rMyP@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).