Your message dated Thu, 3 Mar 2016 22:59:14 +0100
with message-id <20160303215914.gc19...@percival.namespace.at>
and subject line Re: #678512: fixed in sid
has caused the Debian Bug report #678512,
regarding segfaults with IPv6
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 ow...@bugs.debian.org
immediately.)
--
678512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-eventmachine
Version: 0.12.10-3
Severity: important
Tags: ipv6
Please forward this bug upstream. It exists in eventmachine 1.0 (from
gems) too.
Running thin listening on ipv6 address ::1 results in the following
segfault. Listening on IPv4 socket, no problems.
$ thin -a ::1 start -D
>> Using rack adapter
>> Thin web server (v1.5.0 codename Knife)
>> Debugging ON
>> Maximum connections set to 1024
>> Listening on ::1:3000, CTRL+C to stop
*** stack smashing detected ***: ruby1.9.1 terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f00feae72e7]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f00feae72b0]
/home/adamm/.gem/gems/eventmachine-1.0.0/lib/rubyeventmachine.so(_ZN18AcceptorDescriptor4ReadEv+0x1b7)[0x7f00fc9a5b27]
/home/adamm/.gem/gems/eventmachine-1.0.0/lib/rubyeventmachine.so(_ZN14EventMachine_t13_RunEpollOnceEv+0x1d1)[0x7f00fc99d621]
/home/adamm/.gem/gems/eventmachine-1.0.0/lib/rubyeventmachine.so(_ZN14EventMachine_t8_RunOnceEv+0x65)[0x7f00fc99ea85]
/home/adamm/.gem/gems/eventmachine-1.0.0/lib/rubyeventmachine.so(_ZN14EventMachine_t3RunEv+0x58)[0x7f00fc9a0458]
/home/adamm/.gem/gems/eventmachine-1.0.0/lib/rubyeventmachine.so(+0x1c9f9)[0x7f00fc9a89f9]
/usr/lib/libruby-1.9.1.so.1.9(+0x1520a3)[0x7f00ff9b50a3]
/usr/lib/libruby-1.9.1.so.1.9(+0x147f39)[0x7f00ff9aaf39]
/usr/lib/libruby-1.9.1.so.1.9(+0x14d5c4)[0x7f00ff9b05c4]
/usr/lib/libruby-1.9.1.so.1.9(rb_iseq_eval+0x160)[0x7f00ff9b7ac0]
/usr/lib/libruby-1.9.1.so.1.9(+0x609b0)[0x7f00ff8c39b0]
/usr/lib/libruby-1.9.1.so.1.9(+0x60ab9)[0x7f00ff8c3ab9]
/usr/lib/libruby-1.9.1.so.1.9(+0x1520a3)[0x7f00ff9b50a3]
/usr/lib/libruby-1.9.1.so.1.9(+0x147f39)[0x7f00ff9aaf39]
/usr/lib/libruby-1.9.1.so.1.9(+0x14d5c4)[0x7f00ff9b05c4]
/usr/lib/libruby-1.9.1.so.1.9(rb_iseq_eval_main+0xad)[0x7f00ff9b7bad]
/usr/lib/libruby-1.9.1.so.1.9(+0x5de1a)[0x7f00ff8c0e1a]
/usr/lib/libruby-1.9.1.so.1.9(ruby_exec_node+0x1d)[0x7f00ff8c18bd]
/usr/lib/libruby-1.9.1.so.1.9(ruby_run_node+0x1e)[0x7f00ff8c334e]
ruby1.9.1[0x40091b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f00fea16ead]
ruby1.9.1[0x400949]
running c++filt resolves part of the trace to,
AcceptorDescriptor::Read()
EventMachine_t::_RunEpollOnce()
EventMachine_t::_RunOnce()
EventMachine_t::Run()
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.6.7+ (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ruby-eventmachine depends on:
ii libc6 2.13-36
ii libgcc1 1:4.7.2-4
ii libruby1.8 1.8.7.358-5
ii libruby1.9.1 1.9.3.194-3
ii libstdc++6 4.7.2-4
ii ruby 4.9
ii ruby1.8 [ruby-interpreter] 1.8.7.358-5
ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-3
ruby-eventmachine recommends no packages.
ruby-eventmachine suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 ruby-eventmachine/1.0.7-1
Marking as fixed in sid, as all referenced commits are part of
1.0.7, which is in sid.
--
,''`. Christian Hofstaedtler <z...@debian.org>
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
--- End Message ---
