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: Fri, 5 Oct 2001 09:57:37 +0200	[thread overview]
Message-ID: <20011005095737.A1460@sistina.com> (raw)
In-Reply-To: <3BBD6084.70106@st-peter.stw.uni-erlangen.de>; from galia@st-peter.stw.uni-erlangen.de on Fri, Oct 05, 2001 at 09:25:56AM +0200

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.

> 
> 
> Heinz J . Mauelshagen wrote:
> 
> >Markus,
> >
> >go without optimization "-O0" rather than "-O2" in LVMs configure stript
> >*or* with gcc 2.95.2.
> >
> >On Thu, Oct 04, 2001 at 10:33:43PM +0200, Markus Dobel wrote:
> >
> >>Hi,
> >>
> >>vgextend, vgreduce and lvextend segfaulted for me today, too. I'm using 
> >>
> >>  gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-95)
> >>
> >>which I guess is the reason for those problems.
> >>
> >>For vgextend/vgreduce gdb told me, that in vg_extend_reduce "vg_name"
> >>pointed to 0x1. So i did a little debugging and therefore also
> >>inserting the line:
> >>
> >>int vg_extend ( char *vg_name, pv_t *pv, vg_t *vg) {
> >>   printf("VG Name is %s\n",vg_name ); // this one
> >>   return vg_extend_reduce ( vg_name, pv, vg, VG_EXTEND);
> >>}
> >>
> >>in vg_extend_reduce.c, the same in vg_reduce(). Without changing
> >>anything else, vgextend and vgreduce work for me now.
> >>
> >>
> >>Similar in lv_extend_reduce.c:
> >>
> >>int lv_extend ( vg_t *vg, lv_t *lv, char *lv_name) {
> >>   printf("Extending %s\n", lv_name); // added this line.
> >>   return lv_extend_reduce ( vg, lv, lv_name, LV_EXTEND);
> >>}
> >>
> >>I don't speak C too fluently, and I don't know if printf() does some
> >>implicit casting or something or if it's gcc 2.96, but maybe this
> >>information helps a bit in finding the mistake.
> >>
> >>Regards, Markus
> >>
> >>-- 
> >>Spiegel-Leser wissen mehr. Fuer ein Semester-Abo!
> >>http://www.kawo2.rwth-aachen.de/~mdobel/semesterabo.html
> >>
> >>_______________________________________________
> >>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
> >>
> >
> 
> 
> 
> _______________________________________________
> 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-05  7:57 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 [this message]
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
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=20011005095737.A1460@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.