dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60929] [r600-llvm] mono games with opengl are blocking on start
Date: Tue, 27 Aug 2013 05:22:38 +0000	[thread overview]
Message-ID: <bug-60929-502-Qxy1M7PXXC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-60929-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1873 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=60929

--- Comment #18 from Nicholas Miell <nmiell@gmail.com> ---
(In reply to comment #17)
> Thanks for tracking this down.  I think we'll need to extend the LLVM C API
> in order to get access to this variable.  However, looking through the LLVM
> code it looks like the PrettyStackTrace handler is registered by a static
> initializer, so I wonder if setting this variable is enough and if we can
> guarantee that r600g will set this variable before the handler is
> initialized.

I don't think this is true -- IIRC, all the stack traces I saw were the result
of one of the runOnFunction methods (either BBPassManager or FPPassManager, I
wasn't paying attention) creating a PassManagerPrettyStackEntry object.

> Also, this seems to me like it is a bug in LLVM.  Is it common practice for
> libraries to override signal handlers of applications?

Common enough that both Mono and LLVM stomp on each other, but its
unambiguously wrong for a shared library to globally modify signal handlers.
(Temporarily setting a new handler on entry to your library and later restoring
the saved handler before returning is fine, but that only works in the
single-threaded case since handlers aren't per-thread. Arguably modern
applications shouldn't use any signals at all.)

Mono (generally) gets away with it because it uses crazy signals that
applications never touch (SIGPWR is only sent to PID 1 by the kernel on power
failure, SIGXCPU is relic of obsolete job billing infrastructure that nobody
uses), but had the bad luck of LLVM deciding to future-proof itself against all
possible fatal signals.

If I were to be prescriptive, llvm::DisablePrettyStackTrace should be true by
default, should only ever be set by clang, and shouldn't be a global variable.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2780 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-08-27  5:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 21:29 [Bug 60929] New: [r600-llvm] mono games with opengl are blocking on start bugzilla-daemon
2013-02-15 21:29 ` [Bug 60929] " bugzilla-daemon
2013-02-21 21:07 ` bugzilla-daemon
2013-03-25 13:33 ` bugzilla-daemon
2013-05-20 12:21 ` bugzilla-daemon
2013-06-03 16:52 ` bugzilla-daemon
2013-06-05  7:26 ` bugzilla-daemon
2013-07-15 20:22 ` bugzilla-daemon
2013-07-16  9:16 ` bugzilla-daemon
2013-07-16 10:00 ` bugzilla-daemon
2013-07-16 19:38 ` bugzilla-daemon
2013-07-18 17:15 ` bugzilla-daemon
2013-07-20  7:43 ` bugzilla-daemon
2013-07-20  8:07 ` bugzilla-daemon
2013-07-20  9:04 ` bugzilla-daemon
2013-07-22 13:38 ` bugzilla-daemon
2013-08-22 17:17 ` bugzilla-daemon
2013-08-26  9:11 ` bugzilla-daemon
2013-08-26 23:12 ` bugzilla-daemon
2013-08-27  2:34 ` bugzilla-daemon
2013-08-27  5:22 ` bugzilla-daemon [this message]
2013-09-14 18:49 ` bugzilla-daemon
2013-09-27 14:17 ` bugzilla-daemon
2013-10-19 16:50 ` bugzilla-daemon
2013-10-25 12:51 ` bugzilla-daemon
2013-10-31 21:23 ` bugzilla-daemon
2013-11-03 11:28 ` bugzilla-daemon
2013-11-04  8:26 ` bugzilla-daemon
2013-11-11 18:48 ` bugzilla-daemon

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=bug-60929-502-Qxy1M7PXXC@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).