public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Glenn Enright <elinar@ihug.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gzip segmentation fault
Date: Thu, 21 Jul 2005 23:47:20 +1200	[thread overview]
Message-ID: <200507212347.20353.elinar@ihug.co.nz> (raw)
In-Reply-To: <42DF3680.7010704@gmail.com>

On Thu, 21 Jul 2005 17:45, Zac Medico wrote:
> Richard Fish wrote:
> > I will take a look through the gzip source and see if anything
> > interesting shows up.
>
> Richard, you are a saint ;-).  But remember, he said that gunzip only
> segfaults with files that he compressed himself which suggests that the
> files are being corrupted when he compresses them.  You'd thing that gunzip
> would be able to handle the corruption better that segfaulting though.
>
> Zac

Ok just ran gcc-config and found 
lib # gcc-config -l
/usr/bin/gcc-config: line 
583: /etc/env.d/gcc/i686-pc-linux-gnu-3.4.3-20050110: No such file or 
directory
 * /usr/bin/gcc-config: Profile does not exist or invalid setting 
for /etc/env.d/gcc/i686-pc-linux-gnu-3.4.3-20050110
[1] i686-pc-linux-gnu-3.3.5
[2] i686-pc-linux-gnu-3.3.5-hardened
[3] i686-pc-linux-gnu-3.3.5-hardenednopie
[4] i686-pc-linux-gnu-3.3.5-hardenednossp
[5] i686-pc-linux-gnu-3.4.4
[6] i686-pc-linux-gnu-3.4.4-hardened
[7] i686-pc-linux-gnu-3.4.4-hardenednopie
[8] i686-pc-linux-gnu-3.4.4-hardenednopiessp
[9] i686-pc-linux-gnu-3.4.4-hardenednossp

Thats not right. gonna select 5 and take it through glibc (which was failing 
the 'make test') and gzip, see what happens :P
-- 

On ability:
	A dwarf is small, even if he stands on a mountain top;
	a colossus keeps his height, even if he stands in a well.
		-- Lucius Annaeus Seneca, 4BC - 65AD
e
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-21 11:31 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
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 [this message]
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=200507212347.20353.elinar@ihug.co.nz \
    --to=elinar@ihug.co.nz \
    --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