Linux LVM users
 help / color / mirror / Atom feed
From: Sean Burford <sean.burford@adelaide.edu.au>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Segment Failure ,while doing lvcreate
Date: Thu Oct 25 18:36:01 2001	[thread overview]
Message-ID: <3BD8A30D.EB2E4E37@adelaide.edu.au> (raw)
In-Reply-To: 20011025074500.A4615@omnifarious.org

"Eric M. Hopper" wrote:
> On Thu, Oct 25, 2001 at 08:39:35AM -0400, Jason Edgecombe wrote:
> >   recompile lvm tools with the -O0 flag (no optimization).
> > this is because of redhat's 7.x borken gcc compiler
...
>         Does gcc 3.0.1 have this same problem?  Are you sure the bug
> isn't in the code?  (i.e. having a non-volatile variable randomly
> modified under your nose, or some such that would tend to not work so
> well under optimization.)

I've traced it in gdb, and I saw a function (called via an inline) being
given valid arguments but receiving junk arguments.  It looks like the
stack pointer got messed up (I didn't check, I was viewing source not
asm at the time).  Calling the function directly, rather than through
the inline (which only added an argument to the argument list) worked
fine.

Having your arguments corrupted during a function call sure looks like a
compiler bug to me.

-- 
Sean Burford    x34135
ITS Systems Specialist
Adelaide University

  parent reply	other threads:[~2001-10-25 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25  6:44 [linux-lvm] Segment Failure ,while doing lvcreate David Chang
2001-10-25  7:38 ` Thomas Svedberg
2001-10-25  7:38 ` Jason Edgecombe
2001-10-25  7:44   ` Eric M. Hopper
2001-10-25  7:48     ` Jason Edgecombe
2001-10-26  7:56       ` Eric M. Hopper
2001-10-25  8:14     ` Markus Dobel
2001-10-26  7:50       ` Eric M. Hopper
2001-10-25 18:36     ` Sean Burford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-26  8:02 Jean-Eric Cuendet

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=3BD8A30D.EB2E4E37@adelaide.edu.au \
    --to=sean.burford@adelaide.edu.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox