[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#652960: marked as done ([libgomp1] Libgomp crash and segfault some php package)



Your message dated Thu, 12 Jul 2012 10:07:19 +0200
with message-id <CAE2SPAbJJdJ4iUhuPhKEk3j8k+T1a7=7knSYwDhh6HQHNLBB7Q@mail.gmail.com>
and subject line Fixed by upgrade
has caused the Debian Bug report #652960,
regarding [libgomp1] Libgomp crash and segfault some php package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
652960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652960
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libgomp1
Version: 4.6.2-7
Severity: important

Dear gcc maintenair,

It seems they are a bug in libgomp that crash imagemagick particularly php-magick see http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=568349

Backtrace is
#0  do_wait (val=12, addr=0x100f154) at ../../../src/libgomp/config/linux/wait.h:53
#1  gomp_barrier_wait_end (bar=0x100f150, state=12) at ../../../src/libgomp/config/linux/bar.c:49
#2  0x00007ffff1a8964e in gomp_thread_start (xdata=<optimized out>) at ../../../src/libgomp/team.c:119
#3  0x00007ffff49c1b40 in start_thread (arg=<optimized out>) at pthread_create.c:304
#4  0x00007ffff4ec236d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Please check if they are some security implication

Thanks




--- End Message ---
--- Begin Message ---
Hi,

I have upgraded my package (first message was too fast) and it seems
that upgrade solve this problem. Feel free to reopen if it is does not
work on your side

Bastien


--- End Message ---

Reply to: