[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151007072753.GM28311@example.net>
Date: Wed, 7 Oct 2015 09:27:54 +0200
From: u-uy74@...ey.se
To: musl@...ts.openwall.com
Subject: Re: musl bug or not, real or not? (Was: Update:
pthread_getattr_np() vs explicit runtime) loader
On Tue, Oct 06, 2015 at 01:07:55PM -0400, Rich Felker wrote:
> It's not that I'm uninterested, just that there does not yet seem to
> be any reason to believe it's a bug in musl or any easy test-case to
> reproduce the problem, so I wouldn't even know where to get started...
That's why I looked for somebody to do a simple test (even though with
a "complex" application), to see how reproducible the problem is.
The crash (now I assume that it resides in gcc) depends apparently on
a combination of many variables.
> I think you really need to find a way to use what debugging tools you
> have to figure out what's going on and where the actual source of the
> crash is.
Pretty remarkably, neither my usual gdb nor Debian's current gdb were
able to make sence of the crashes. Probably the thread states became
messed up too badly.
Fortunately I do not think any longer that musl is the culprit, nor do
I actually need gcj, otherwise have a workaround. Will not pursue this
issue further.
Thanks for your feedback, sorry for the noise.
Rune
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
