public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gzip segmentation fault
Date: Wed, 20 Jul 2005 10:09:19 -0700	[thread overview]
Message-ID: <42DE853F.7090604@gmail.com> (raw)
In-Reply-To: <200507202228.14489.elinar@ihug.co.nz>

Glenn Enright wrote:
> On Wed, 20 Jul 2005 21:26, Zac Medico wrote:
> 
>>Does busybox gzip work any better?
>>
>>Zac
> 
> 
> Yes works just fine. What does that tell you?
> 

You have a workaround ;-).  The problem seems to be in glibc (only dependency of gzip, verified by "ldd `which gzip`") or your toolchain.  You might be able to get some clues from gdb or strace, but whatever the cause, you probably need to replace glibc and/or your toolchain.

I wonder if static linking would help gzip?

USE=static emerge gzip

Zac
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-20 17:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19  4:34 [gentoo-user] gzip segmentation fault Glenn Enright
2005-07-19  4:56 ` Zac Medico
2005-07-19 12:32   ` Glenn Enright
2005-07-20  7:36     ` Glenn Enright
2005-07-20  7:33       ` Zac Medico
2005-07-20  8:08         ` Glenn Enright
2005-07-20  8:02           ` Zac Medico
2005-07-20  8:18         ` Glenn Enright
2005-07-20  9:26           ` Zac Medico
2005-07-20 10:28             ` Glenn Enright
2005-07-20 17:09               ` Zac Medico [this message]
2005-07-20 21:54                 ` Glenn Enright
2005-07-20 22:02                   ` Zac Medico
2005-07-21  6:24                     ` Glenn Enright
2005-07-21  5:33                   ` Richard Fish
2005-07-21  5:45                     ` Zac Medico
2005-07-21 11:47                       ` Glenn Enright
2005-07-21 20:32                         ` Richard Fish
2005-07-22  4:00                           ` Glenn Enright
2005-07-22  4:41                             ` Zac Medico

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

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

  git send-email \
    --in-reply-to=42DE853F.7090604@gmail.com \
    --to=zmedico@gmail.com \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox