public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "rschoppmeyer at vmware dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/17580] New: GDB fails to inspect a particular class
Date: Tue, 11 Nov 2014 20:15:00 -0000	[thread overview]
Message-ID: <bug-17580-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17580
           Summary: GDB fails to inspect a particular class
           Product: gdb
           Version: 7.7
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: rschoppmeyer at vmware dot com

Created attachment 7923
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7923&action=edit
reproducing example

Skim instructions in README (included in attached file).

Platform: Ubuntu 14.04.1
Compiler: Ubuntu clang version 3.4-1ubuntu3 (tags/RELEASE_34/final) (based on
LLVM 3.4)
GDB:      GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1

See attached file for a concise reproducing example.
notmain.cc contains a class NetInfo with a single member, `name` of class
String.
The `String` class is a subclass of std::string declared in notstring.hh.

Attempting to `print info` in GDB after its declaration yields:
(gdb) p info
$1 = {name = <error reading variable>

Attempting to `print info.name` produces the rather nonsensical error message:
(gdb) p info.name
That operation is not available on integers of more than 8 bytes.

Printing any other instance of the NetInfo class is aborted in a similar
manner.  Observe that printing the class is truncated, no closing '}' is
printed.  If there are other members in NetInfo following `name`, they are
omitted.  If you try to print a class that contains a member of type NetInfo,
printing moves on to that class' next member after aborting printing NetInfo.

If you compile the attached file as a single execution unit (`make monolith`),
this issue is not reproducible.

I guess it's also possible that this is a clang bug.

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


             reply	other threads:[~2014-11-11 20:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 20:15 rschoppmeyer at vmware dot com [this message]
2014-11-11 20:35 ` [Bug c++/17580] " sivachandra at gmail 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-17580-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).