From: Michael Marxmeier <mike@msede.com>
To: Chris Anderson <chris@alwan.com>
Cc: "linux-lvm@msede.com" <linux-lvm@msede.com>
Subject: Re: [linux-lvm] Trouble 2.2.14 setup - unresolved symbol lvm_map_ptr (My first time)
Date: Sun, 30 Jan 2000 22:39:19 +0100 [thread overview]
Message-ID: <3894AF87.E9DF6C58@msede.com> (raw)
In-Reply-To: 3894AD20.F826BEFF@alwan.com
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 ?
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/
next prev parent reply other threads:[~2000-01-30 21:39 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 [this message]
2000-01-30 21:51 ` [linux-lvm] Trouble 2.2.14 setup " Chris Anderson
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=3894AF87.E9DF6C58@msede.com \
--to=mike@msede.com \
--cc=chris@alwan.com \
--cc=linux-lvm@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