Fwd: Bug report on eperl: eperl crashes with exit status 139 [origin: alexan...@cmu.edu]

2013-06-26 Thread Axel Beckert
Hi eglibc maintainers, the attached crash in eperl looks like a bug in getopt_long of libc6 to me: [ 18.024562] eperl[2718]: segfault at 1 ip b74b0d4f sp bf9457ec error 4 in libc-2.17.so[b7433000+1a9000] Backtrace: Program received signal SIGSEGV, Segmentation fault. __strlen_sse2 () at

Re: Fwd: Bug report on eperl: eperl crashes with exit status 139 [origin: alexan...@cmu.edu]

2013-06-26 Thread Bastian Blank
On Thu, Jun 27, 2013 at 01:07:13AM +0200, Axel Beckert wrote: #3 0x770e5783 in getopt_long (argc=1, argv=0x7fffe228, options=0x0, long_options=0x1, opt_index=0x0) at getopt1.c:66 Why are the options and long_options arguments shown with nonsense contents? Bastian -- In the

Re: Fwd: Bug report on eperl: eperl crashes with exit status 139 [origin: alexan...@cmu.edu]

2013-06-26 Thread Aurelien Jarno
On Thu, Jun 27, 2013 at 01:07:13AM +0200, Axel Beckert wrote: Hi eglibc maintainers, the attached crash in eperl looks like a bug in getopt_long of libc6 to me: [ 18.024562] eperl[2718]: segfault at 1 ip b74b0d4f sp bf9457ec error 4 in libc-2.17.so[b7433000+1a9000] Backtrace:

Re: Fwd: Bug report on eperl: eperl crashes with exit status 139 [origin: alexan...@cmu.edu]

2013-06-26 Thread Axel Beckert
Hi Aurelien! Aurelien Jarno wrote: I object. The problem is clearly on the eperl side, which passes to getopt_long an option structure not ended by { 0, 0, 0, 0 }. Thanks for that hint! Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ :