All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] More Segfaults with LVM 1.0.1rc3
Date: Mon, 8 Oct 2001 12:02:07 +0200	[thread overview]
Message-ID: <20011008120207.A18314@sistina.com> (raw)
In-Reply-To: <20011006231826.A739@guldukat.muon.local>; from nils@muon.de on Sat, Oct 06, 2001 at 11:18:26PM +0000

Nile,
thanks for the info.

Does LVM compiled under gcc-3.0.1 *without* optimization work?

On Sat, Oct 06, 2001 at 11:18:26PM +0000, Nils Juergens wrote:
> On Fri, 05.10.01, svetljo <galia@st-peter.stw.uni-erlangen.de> wrote:
> > 
> > Heinz J . Mauelshagen wrote:
> > 
> > >On Fri, Oct 05, 2001 at 09:25:56AM +0200, svetljo wrote:
> > >
> > >>is gcc-3.0.1 safe, or i should also use "-o0"
> > >>
> > >
> > >Don't have a report for this :-(
> > >Please try it.
> > >
> > it's seems to work
> > 
> 
> I tried gcc-3.0.1 with LVM on linux-2.4.10 and had a lot of problems,
> but it was no problem in LVM, it works with 2.95.4.
> 
> What i was seeing was funny stuff happening to the stack after
> a function call causing (in my case) lvremove to segfault.
> I have seen this with gcc-3.0.1 before, on another program.
> 
> 
> Nils
> 
> -- 
>  >   Nils Juergens  | nils@muon.de | icq 7090774   <
>  >  If we all work hard, we can turn this company  <
>  >      around 360 degrees -- gruntbert(LOTD)      <
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-10-08 10:02 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 [this message]
2001-10-10 21:41             ` Nils Juergens
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=20011008120207.A18314@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.