On Fri, Sep 16, 2016 at 08:38:34AM -0500, Bob Friesenhahn wrote:
> On Fri, 16 Sep 2016, László Böszörményi wrote:
> This is all very strange. I am not seeing a problem with the source code.
> I thought that the crash was happening at line 301 of log.c (at
> LockSemaphoreInfo()), and the first
On Fri, Sep 16, 2016 at 3:38 PM, Bob Friesenhahn
wrote:
> On Fri, 16 Sep 2016, László Böszörményi wrote:
>> On Fri, Sep 16, 2016 at 11:56 AM, Niko Tyni wrote:
>>> I've bisected it to
>>>
On Fri, 16 Sep 2016, László Böszörményi wrote:
On Fri, Sep 16, 2016 at 11:56 AM, Niko Tyni wrote:
On Tue, Sep 13, 2016 at 10:48:42PM -0500, Bob Friesenhahn wrote:
It may be necessary to prove where the problem is occuring by manually
overwriting updated files in the magick
On Fri, Sep 16, 2016 at 11:56 AM, Niko Tyni wrote:
> On Tue, Sep 13, 2016 at 10:48:42PM -0500, Bob Friesenhahn wrote:
>> It may be necessary to prove where the problem is occuring by manually
>> overwriting updated files in the magick directory with those from the
>> previous
On Fri, Sep 16, 2016 at 12:56:37PM +0300, Niko Tyni wrote:
> I haven't found the exact optimization that's triggering it yet,
At -O1 it goes away with -fno-inline-functions-called-once .
> and I haven't looked at the code GCC generates.
Diffstat for timer.s between -O1 and "-O1
On Tue, Sep 13, 2016 at 10:48:42PM -0500, Bob Friesenhahn wrote:
> It may be necessary to prove where the problem is occuring by manually
> overwriting updated files in the magick directory with those from the
> previous working version until the problem goes away (assuming that it
> does).
I've
On Wed, 14 Sep 2016, László Böszörményi wrote:
As Perl debug and libc6 debug symbols installed, I don't know which
library / executable may contain points #0 and #1. Maybe log.c itself?
At least the mentioned line in #2 is:
LockSemaphoreInfo(log_semaphore);
There were no functions added or
Hi Bob, Niko,
On Tue, Sep 13, 2016 at 11:15 PM, Bob Friesenhahn
wrote:
> On Tue, 13 Sep 2016, László Böszörményi wrote:
>> On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni wrote:
>>> This package is failing to build on ppc64el, but built successfully
On Tue, 13 Sep 2016, László Böszörményi wrote:
On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni wrote:
This package is failing to build on ppc64el, but built successfully
in the past. As seen at
https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=ppc64el
it regressed
On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni wrote:
> This package is failing to build on ppc64el, but built successfully
> in the past. As seen at
> https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=ppc64el
> it regressed with 1.3.24+hg20160808-1, and the version
Package: graphicsmagick
Version: 1.3.25-1
Severity: serious
This package is failing to build on ppc64el, but built successfully
in the past. As seen at
https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=ppc64el
it regressed with 1.3.24+hg20160808-1, and the version currently in
sid is
11 matches
Mail list logo