kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: kgio@librelist.org
Subject: Re: version 2.7.3 crashes on sparc under ruby1.9
Date: Fri, 10 Aug 2012 20:10:52 +0000	[thread overview]
Message-ID: <20120810201052.GA27144@dcvr.yhbt.net> (raw)
In-Reply-To: CAAB-Kcm8RY8ZJqQCqnyvi5FPU3L4At7Mfhm_sw6jcn1Qyu9c+Q@mail.gmail.com

Hleb Valoshka <375gnu@gmail.com> wrote:
> Hallo,
> 
> Eric, could you look at this build logs: [1], [2]. I have no idea what
> goes wrong with sparc and, to tell the truth, I've never seen any
> sparc machine (qemu-system-sparc doesn't work with current debian).
> 
> 2.7.3 crashes with ruby 1.9.3.0 and 1.9.3.194 but 2.7.2 was ok with 1.9.3.0 [3].

I doubt the changes from 2.7.2 -> 2.7.3 could've caused crashes, I
suspect something else in the stack (eglibc?) broke between them.

Does 2.7.4 work?

> [1] https://buildd.debian.org/status/fetch.php?pkg=ruby-kgio&arch=sparc&ver=2.7.3-1&stamp=1343565141
> 
> [2] https://buildd.debian.org/status/fetch.php?pkg=ruby-kgio&arch=sparc&ver=2.7.3-1&stamp=1331843923
> 1.9.3.0
> 
> [3] https://buildd.debian.org/status/fetch.php?pkg=ruby-kgio&arch=sparc&ver=2.7.2-1&stamp=1329783946

Hopefully the Debian SPARC maintainers can help narrow this down.  I
suspect other Ruby software has similar failures, too.  It's definitely
low priority for me (and probably you :)).

Somebody who cares about the platform should investigate.

If it makes your life easier, I wouldn't mind at all if you mark kgio as
unsupported on rare Debian platforms.  x86-64/x86 are my main
priorities.


  reply	other threads:[~2012-08-10 20:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 17:17 version 2.7.3 crashes on sparc under ruby1.9 Hleb Valoshka
2012-08-10 20:10 ` Eric Wong [this message]
2012-08-10 20:32   ` Hleb Valoshka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/kgio/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120810201052.GA27144@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=kgio@librelist.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/kgio.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).