From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org, jan.kratochvil@redhat.com
Subject: [patch] document that check_typedef can throw an exception
Date: Thu, 27 Oct 2011 22:03:00 -0000 [thread overview]
Message-ID: <20111027215551.97B0C246191@ruffy.mtv.corp.google.com> (raw)
Hi.
I will check this in in a few days if there are no objections.
2011-10-27 Doug Evans <dje@google.com>
* gdbtypes.c (check_typedef): Document that this function can
throw an exception.
Index: gdbtypes.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtypes.c,v
retrieving revision 1.220
diff -u -p -r1.220 gdbtypes.c
--- gdbtypes.c 14 Oct 2011 20:22:17 -0000 1.220
+++ gdbtypes.c 27 Oct 2011 21:53:52 -0000
@@ -1454,6 +1454,9 @@ stub_noname_complaint (void)
not been computed and we're either in the middle of reading symbols, or
there was no name for the typedef in the debug info.
+ NOTE: Lookup of types for opaque types can throw some errors during
+ invalid symbol files. Thus this function can throw an exception.
+
If TYPE is a TYPE_CODE_TYPEDEF, its length is updated to the length of
the target type.
next reply other threads:[~2011-10-27 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 22:03 Doug Evans [this message]
2011-10-28 3:40 ` Jan Kratochvil
2011-11-10 8:05 ` Doug Evans
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=20111027215551.97B0C246191@ruffy.mtv.corp.google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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