From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Move printing of TLS related error messages to dwarf2loc.c
Date: Fri, 18 Mar 2005 21:05:00 -0000 [thread overview]
Message-ID: <20050318140538.2645f56c@ironwood.lan> (raw)
In-Reply-To: <20050310133357.4f9daa6e@ironwood.lan>
On Thu, 10 Mar 2005 13:33:57 -0700
Kevin Buettner <kevinb@redhat.com> wrote:
> * Makefile.in (dwarf2loc.o, linux-thread-db.o): Add dependencies.
> * exceptions.h (TLS_NO_LIBRARY_SUPPORT_ERROR, TLS_GENERIC_ERROR)
> (TLS_LOAD_MODULE_NOT_FOUND_ERROR, TLS_NOT_ALLOCATED_YET_ERROR):
> New error/exception enums.
> * dwarf2loc.c (exceptions.h): Include.
> (dwarf_expr_tls_address): Invoke target_get_thread_local_address()
> via TRY_CATCH mechanism. Print error messages for TLS related
> exceptions.
> * linux-thread-db.c (thread_db_get_thread_local_address): Throw
> exceptions instead of printing errors.
Committed.
Kevin
prev parent reply other threads:[~2005-03-18 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 20:34 Kevin Buettner
2005-03-10 20:43 ` Daniel Jacobowitz
2005-03-18 21:05 ` Kevin Buettner [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=20050318140538.2645f56c@ironwood.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.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