From: Chris Anderson <chris@alwan.com>
To: Michael Marxmeier <mike@msede.com>,
"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 15:29:04 -0600 [thread overview]
Message-ID: <3894AD20.F826BEFF@alwan.com> (raw)
In-Reply-To: 200001301944.UAA20420@e35.marxmeier.com
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
Michael Marxmeier wrote:
> > IMO there's no obvious reason, why it should core there with size == 8.
> >
> > Do you have an old libc in place by accident which might give us a
> > reason to assume an broken malloc()?
> > If so: try with an actual one.
> >
> > Any ideas from other list members?
>
> Conventional wisdom tells that when malloc crashes the free list
> (aka arena) has been trashed. This can happen eg. by a double free
> (some malloc versions check against this) or by writing beyond the
> end of a buffer.
>
> You might want to try the following:
> env MALLOC_CHECK_=1 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?
>
> This will use a debugging version of malloc which might print
> sone diagnostics to stderr if a problem is encountered.
>
> see malloc(3) for additional information.
>
> Hope this helps
> 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 --]
next prev parent reply other threads:[~2000-01-30 21:29 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 [this message]
2000-01-30 21:39 ` Michael Marxmeier
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=3894AD20.F826BEFF@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 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.