From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Generate unwind info for pthread_sighandler*
Date: Thu, 02 May 2002 07:55:00 -0000 [thread overview]
Message-ID: <20020502165539.M32482@sunsite.ms.mff.cuni.cz> (raw)
Hi!
I think one should be able to unwind through the pthread
signal handler wrappers (e.g. libjava currently uses very ugly workarounds
because of this).
Or would you prefer instead moving those 2 functions into separate source
file and add exceptions just to that file?
2002-05-02 Jakub Jelinek <jakub@redhat.com>
* Makefile (CFLAGS-signals.c): Build unwind info.
--- linuxthreads/Makefile.jj Wed Jan 30 18:01:24 2002
+++ linuxthreads/Makefile Thu May 2 16:57:10 2002
@@ -80,6 +80,7 @@ CFLAGS-pthread.c += -D__NO_WEAK_PTHREAD_
CFLAGS-ptfork.c += -D__NO_WEAK_PTHREAD_ALIASES
CFLAGS-cancel.c += -D__NO_WEAK_PTHREAD_ALIASES -D_RPC_THREAD_SAFE_
CFLAGS-unload.c += -DPREFIX=\"$(objpfx)\"
+CFLAGS-signals.c += $(exceptions)
# Depend on libc.so so a DT_NEEDED is generated in the shared objects.
# This ensures they will load libc.so for needed symbols if loaded by
Jakub
next reply other threads:[~2002-05-02 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 7:55 Jakub Jelinek [this message]
2002-05-03 0:39 ` Ulrich Drepper
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=20020502165539.M32482@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).