From: Dave Jones <davej@suse.de>
To: jay <jbeatty@optonline.net>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: rpm --rebuild fails on 2.5.20
Date: Sat, 8 Jun 2002 21:55:20 +0200 [thread overview]
Message-ID: <20020608215520.D13140@suse.de> (raw)
In-Reply-To: <3D0249AE.4070902@optonline.net>
On Sat, Jun 08, 2002 at 02:15:10PM -0400, jay wrote:
> When I try to use rpm to rebuild a src.rpm, it gives a Segmentation
> fault on 2.5.20. Works on 2.5.18 and 2.4.18.
>
> rpm -vvvvvv --rebuild ORBit2*
> Segmentation fault
> Some small src.rpm files work, e.g. filesystem-2.1.6-4.src.rpm, but not all.
can you strace an operation that fails, and find out where it's
segfaulting. Also, check dmesg for a kernel oops, and decode
with kysmoops if present.
I've one other report of a problem with capabilities, which
might be related.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-06-08 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 18:15 rpm --rebuild fails on 2.5.20 jay
2002-06-08 19:55 ` Dave Jones [this message]
[not found] <linux.kernel.20020608215520.D13140@suse.de>
2002-06-10 3:00 ` sean darcy
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=20020608215520.D13140@suse.de \
--to=davej@suse.de \
--cc=jbeatty@optonline.net \
--cc=linux-kernel@vger.kernel.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