public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Segmentation fault on Emerge -S
Date: Thu, 12 Oct 2006 10:58:18 +0200	[thread overview]
Message-ID: <200610121058.21689.bo.andresen@zlin.dk> (raw)
In-Reply-To: <20061012045955.47a66ce6@owl.gotdns.org>

[-- Attachment #1: Type: text/plain, Size: 560 bytes --]

On Thursday 12 October 2006 09:59, Wagner Vaz wrote:
> It's a bit funny if not sad. Just look:
>
> #emerge -S netrw
> Searching... |Segmentation fault
>
> What is these?

It really would help if we knew what version you were running. Try this:

# emerge -u portage

# emerge -u python

# python-updater

# revdep-rebuild

If after that you still see the above behaviour:

# emerge --debug -S netrw &> debug.log
# gzip debug.log

Then attach debug.log.gz and post that together with the output of:

# emerge --info

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-10-12  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12  7:59 [gentoo-user] Segmentation fault on Emerge -S Wagner Vaz
2006-10-12  8:35 ` Alan McKinnon
2006-10-12  8:58 ` Bo Ørsted Andresen [this message]
2006-10-12 18:38   ` Wagner Vaz

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=200610121058.21689.bo.andresen@zlin.dk \
    --to=bo.andresen@zlin.dk \
    --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