public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/17018] New: XFAIL: gdb.go/hello.exp: Starting string check
Date: Wed, 04 Jun 2014 13:18:00 -0000	[thread overview]
Message-ID: <bug-17018-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=17018

            Bug ID: 17018
           Summary: XFAIL: gdb.go/hello.exp: Starting string check
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: go
          Assignee: unassigned at sourceware dot org
          Reporter: palves at redhat dot com

On Fedora 20, I noticed this:

print st
$1 = 0xc200016210 "\000\000\000\000\000\000\000\000\200c\000\000\302", '\000'
<repeats 11 times>,
"d\000\000\000\000\000\000\000P$\322\367\377\177\000\000\000\000\000\000\0
00\000\000\000pb\001\000\302", '\000' <repeats 43 times>, "\240b\001\000\302",
'\000' <repeats 43 times>, "\320b\001\000\302", '\000' <repeats 44 times>,
"c\001\000\302\000
\000\000"...
(gdb) XFAIL: gdb.go/hello.exp: Starting string check

The comment in the test says this is XFAIL for a different reason:

# This used to print "", i.e., the local "st" initialized as "".
setup_xfail "*-*-*"

gdb_test "print st" \
    ".* = $hex \"\"" \
    "Starting string check"

So I wonder if this is really expected.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


                 reply	other threads:[~2014-06-04 13:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-17018-4717@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).