From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] document that check_typedef can throw an exception
Date: Fri, 28 Oct 2011 03:40:00 -0000 [thread overview]
Message-ID: <20111028020913.GA4765@host1.jankratochvil.net> (raw)
In-Reply-To: <20111027215551.97B0C246191@ruffy.mtv.corp.google.com>
On Thu, 27 Oct 2011 23:55:51 +0200, Doug Evans wrote:
[...]
> * gdbtypes.c (check_typedef): Document that this function can
> throw an exception.
[...]
> + NOTE: Lookup of types for opaque types can throw some errors during
> + invalid symbol files. Thus this function can throw an exception.
Always by expanding opaque types:
Either lookup_symbol_aux_quick:
error (_("\
Internal: %s symbol `%s' found in %s psymtab but not in symtab.\n\
which is not completely correct but it was commonly happenning and it still
may happen.
Or just RETURN_QUIT from new CUs being expanded
...->dwarf2_compute_name->c_print_type->... (there some QUIT; statements).
Regards,
Jan
next prev parent reply other threads:[~2011-10-28 2:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 22:03 Doug Evans
2011-10-28 3:40 ` Jan Kratochvil [this message]
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=20111028020913.GA4765@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@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