From: Nils Juergens <nils@muon.de>
To: linux-lvm@sistina.com
Cc: mauelshagen@sistina.com
Subject: Re: [linux-lvm] More Segfaults with LVM 1.0.1rc3
Date: Wed, 10 Oct 2001 23:41:58 +0200 [thread overview]
Message-ID: <20011010234158.A14457@muon.de> (raw)
In-Reply-To: <20011008120207.A18314@sistina.com>
On Mon, 08.10.01, "Heinz J . Mauelshagen" <mauelshagen@sistina.com> wrote:
>
> Does LVM compiled under gcc-3.0.1 *without* optimization work?
>
No, with -O0 i get the same seg'fault.
Nils
--
> Nils Juergens | nils@muon.de | icq 7090774 <
> If we all work hard, we can turn this company <
> around 360 degrees -- gruntbert(LOTD) <
next prev parent reply other threads:[~2001-10-10 21:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 20:33 [linux-lvm] More Segfaults with LVM 1.0.1rc3 Markus Dobel
2001-10-05 7:08 ` Heinz J . Mauelshagen
2001-10-05 7:25 ` svetljo
2001-10-05 7:57 ` Heinz J . Mauelshagen
2001-10-05 8:15 ` svetljo
2001-10-06 23:18 ` Nils Juergens
2001-10-08 10:02 ` Heinz J . Mauelshagen
2001-10-10 21:41 ` Nils Juergens [this message]
2001-10-07 12:30 ` svetljo
2001-10-08 10:03 ` Heinz J . Mauelshagen
2001-10-09 0:25 ` Paul Jakma
2001-10-09 0:40 ` Luca Berra
2001-10-09 7:42 ` Joe Thornber
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=20011010234158.A14457@muon.de \
--to=nils@muon.de \
--cc=linux-lvm@sistina.com \
--cc=mauelshagen@sistina.com \
/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;
as well as URLs for NNTP newsgroup(s).