Linux LVM users
 help / color / mirror / Atom feed
From: Chris Anderson <chris@alwan.com>
To: Michael Marxmeier <mike@msede.com>
Cc: "linux-lvm@msede.com" <linux-lvm@msede.com>
Subject: Re: [linux-lvm] Trouble 2.2.14 setup (My first time)
Date: Sun, 30 Jan 2000 15:51:45 -0600	[thread overview]
Message-ID: <3894B271.6BB2381@alwan.com> (raw)
In-Reply-To: 3894AF87.E9DF6C58@msede.com

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

Michael Marxmeier wrote:

> Chris Anderson wrote:
> >
> > Michael Marxmeier wrote:
> > > You might want to try the following:
> > > env vgcreate ...
> >
> > This is printed out when I set the check.  Also it does not crash if I set
> > it to 1.
> >
> > malloc: using debugging hooks
> > realloc(): invalid pointer 0x804b730!
> >
> > Whats next?  Should I look for a double free?
>
> Probably. If you set MALLOC_CHECK_=2 you get an instanteous
> core dump (by the virtue of abort()) so you can fire up your
> favourite debugger and look the call chain.
>
> This suspicously looks like the bug documented in
> http://linux/lvm/doc/BUGS
>
> You _did_ make the suggested fix for
> tools/lib/lvm_tab_vg_check_exist_all_vg.c ?

Yes, I did what the bug list asked me to do.  That is how I got the other tools
to work.

I do not see where the "vgdisplay -A" command  uses that area of code from the
bug list.

>
>
> Michael
>
> --
> Michael Marxmeier           Marxmeier Software AG
> E-Mail: mike@msede.com      Besenbruchstrasse 9
> Phone : +49 202 2431440     42285 Wuppertal, Germany
> Fax   : +49 202 2431420     http://www.msede.com/

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2550 bytes --]

      reply	other threads:[~2000-01-30 21:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-29 20:24 [linux-lvm] Trouble 2.2.14 setup - unresolved symbol lvm_map_ptr (My first time) Michael Marxmeier
2000-01-30  0:26 ` Chris Anderson
2000-01-30  0:32   ` Heinz Mauelshagen
2000-01-30  1:07     ` Chris Anderson
2000-01-30  1:51       ` Heinz Mauelshagen
2000-01-30  2:32         ` Chris Anderson
2000-01-30 13:56           ` Heinz Mauelshagen
2000-01-30 15:49             ` Chris Anderson
2000-01-30 18:13               ` Heinz Mauelshagen
2000-01-30 19:44                 ` Michael Marxmeier
2000-01-30 20:57                   ` Andi Kleen
2000-01-30 21:29                   ` Chris Anderson
2000-01-30 21:39                     ` Michael Marxmeier
2000-01-30 21:51                       ` Chris Anderson [this message]

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=3894B271.6BB2381@alwan.com \
    --to=chris@alwan.com \
    --cc=linux-lvm@msede.com \
    --cc=mike@msede.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