From: Tom Tromey <tromey@redhat.com>
To: "Saraswati\, Sujoy \(JCTL-MCBS\)" <sujoy.saraswati@hp.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Query regarding new dwarf type support in gdb
Date: Fri, 19 Oct 2012 17:17:00 -0000 [thread overview]
Message-ID: <87mwziv0tv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5379BA8D7E9D7E4D87BF6749A92854C239426FF5@G2W2431.americas.hpqcorp.net> (Sujoy Saraswati's message of "Fri, 19 Oct 2012 10:54:42 +0000")
>>>>> "Sujoy" == Saraswati, Sujoy (JCTL-MCBS) <sujoy.saraswati@hp.com> writes:
Sujoy> Ok, I could check the behavior. In general, is there any place where I
Sujoy> can check for current debug support of FSF gdb for C++11 features ?
Just searching around in gdb/dwarf2read.c; and somtimes other dwarf*.c
files.
Sujoy> Yes, I agree. It would be good if we could continue reading the rest
Sujoy> of the debug information from the file even if we face an unknown
Sujoy> type.
I think this specific case should work ok.
Tom
prev parent reply other threads:[~2012-10-19 17:17 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)
2012-10-19 17:17 ` Tom Tromey [this message]
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=87mwziv0tv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=sujoy.saraswati@hp.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).