From: "Saraswati, Sujoy (JCTL-MCBS)" <sujoy.saraswati@hp.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Query regarding new dwarf type support in gdb
Date: Fri, 19 Oct 2012 10:55:00 -0000 [thread overview]
Message-ID: <5379BA8D7E9D7E4D87BF6749A92854C239426FF5@G2W2431.americas.hpqcorp.net> (raw)
In-Reply-To: <87wqynwkr6.fsf@fleche.redhat.com>
Hi Tom,
Thanks for your reply. I have some further comment below -
> I think gdb should issue a complaint (try "set complaints 1000") and
> then make a new TYPE_CODE_ERROR type.
>
> IIRC, g++ already emis rvalue references, but gdb doesn't handle them
> yet.
> You can see this in action by digging around in libstdc++, or maybe
> using gdb with complaints enabled and "file -readnow ...".
Ok, I could check the behavior. In general, is there any place where I can check for current debug support of FSF gdb for C++11 features ?
> We try to avoid calling 'error' during DWARF reading (not with complete
> success) since it tends to discard the whole file's debuginfo -- much
> too big a hammer. This area could use some fixes.
Yes, I agree. It would be good if we could continue reading the rest of the debug information from the file even if we face an unknown type.
Regards,
Sujoy
> Tom
next prev parent reply other threads:[~2012-10-19 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 9:29 Saraswati, Sujoy (JCTL-MCBS)
2012-10-18 21:09 ` Tom Tromey
2012-10-19 10:55 ` Saraswati, Sujoy (JCTL-MCBS) [this message]
2012-10-19 17:17 ` Tom Tromey
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=5379BA8D7E9D7E4D87BF6749A92854C239426FF5@G2W2431.americas.hpqcorp.net \
--to=sujoy.saraswati@hp.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.com \
/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).