Wyciek pamięci w rpm-5.4.12-2? A może glibc-2.18-2 jest skopany?

[Arkadiusz Miśkiewicz]

On Friday 20 of September 2013, stacho wrote:

> Ja z glibc-2.18-1 mam inny problem, nie działa program w javie:
> ==========================
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0xb7658552, pid=12248, tid=3062651712
> #
> # JRE version: 6.0_45-b06
> # Java VM: Java HotSpot(TM) Server VM (20.45-b01 mixed mode linux-x86 )
> # Problematic frame:
> # C  [libc.so.6+0x125552]  __nss_passwd_lookup+0x3ef
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
> 
> ---------------  T H R E A D  ---------------
> 
> Current thread (0xb6704800):  JavaThread "Unknown thread"
> [_thread_in_vm, id=12249, stack(0xb6875000,0xb68c6000)]
> 
> siginfo:si_signo=SIGSEGV: si_errno=0, si_code=128 (),
> si_addr=0x00000000
> 
> =========================
> 
> glibc-2.17 nie ma tego problemu. :(

glibc 2.18-2 też nie powinno go być

-- 
Arkadiusz Miśkiewicz, arekm / maven.pl