From: Daniel Iliev <danny@ilievnet.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Seg Faults
Date: Sun, 24 Dec 2006 23:30:23 +0200 [thread overview]
Message-ID: <458EF16F.9050902@ilievnet.com> (raw)
In-Reply-To: <458EE849.7040504@verizon.net>
sean wrote:
> Ever since upgrading GCC some apps, after emerging from portage, get
> segmentation faults when I try to start them.
>
> Suggestions on what I might be able to do to cure this problem?
> I am guessing that I should enter bugs?
> If so, what would be the best info to enter for the bug report?
>
> Thanks
> Sean
>
Hi,
Have you tried "revdep-rebuild"?
I wouldn't go so fast on reporting bugs - checking false bugs wastes
developers time. So if I were you I would try to solve the problem here
in the user list first. Try revdep-rebuild if you haven't already done this.
P.S.
FYI: It is called "thread hijacking" when someone replies to a letter on
different topic and changes the subject. This irritates many people and
especially the original poster. The normal way to open a new thread is
to write a new letter to the list. All replies are placed in the thread
which you replied to, changing the subject doesn't matter.
--
Best regards,
Daniel
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-12-24 21:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 17:25 [gentoo-amd64] Amarok plugin problem Mark Haney
2006-12-20 17:58 ` Neil Bothwick
2006-12-20 18:20 ` Mark Haney
2006-12-20 18:54 ` Richard Freeman
2006-12-21 5:21 ` Denis Solaro
2006-12-21 22:30 ` [gentoo-amd64] " Harm Geerts
2006-12-20 19:00 ` Duncan
2006-12-20 21:10 ` [gentoo-amd64] " Kevin Koltzau
2006-12-22 21:05 ` Richard Freeman
2006-12-24 20:51 ` [gentoo-amd64] Seg Faults sean
2006-12-24 21:30 ` Daniel Iliev [this message]
2006-12-24 21:40 ` sean
2006-12-25 0:20 ` Daniel Iliev
2006-12-25 20:07 ` Michel Merinoff
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=458EF16F.9050902@ilievnet.com \
--to=danny@ilievnet.com \
--cc=gentoo-amd64@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