From owner-freebsd-bugs  Fri Apr 12 08:49:10 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA13271
          for bugs-outgoing; Fri, 12 Apr 1996 08:49:10 -0700 (PDT)
Received: from mail.internet.com (yipee-p.internet.com [198.183.190.115])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA13224
          for <freebsd-bugs@FreeBSD.ORG>; Fri, 12 Apr 1996 08:48:59 -0700 (PDT)
Received: from oneida.internet.com (oneida.internet.com [198.183.190.138]) by mail.internet.com (8.7.5/8.7.3) with ESMTP id LAA20136; Fri, 12 Apr 1996 11:48:52 -0400 (EDT)
Received: (from reichert@localhost) by oneida.internet.com (8.7.3/8.7.3) id LAA01824; Fri, 12 Apr 1996 11:48:53 -0400 (EDT)
From: Brian Reichert <reichert@oneida.internet.com>
Message-Id: <199604121548.LAA01824@oneida.internet.com>
Subject: mSQL and FreeBSD
To: msql-list@bunyip.com
Date: Fri, 12 Apr 1996 11:48:52 -0400 (EDT)
Cc: freebsd-bugs@FreeBSD.ORG
Reply-To: reichert@internet.com
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I have to pipe up; I'm running into problems, and seek insight:

I have successfully built and tested mSQL 1.0.10 and 1.0.13 under
FreeBSD 2.1R.

I've been successfully using for for all sort of little things,
and it seemed well-behaved.

I recently invented a large table (360k lines, 13 columns), which
seemed to be inserted correctly.

However: my efforts to use msqldump generate a coredump.  Certain
queries ( I tried one that should have returned a thousand one-column
records ) reveal that there is a nasty memory leak somewhere.

When I set the server's debug variable to 'malloc', when I shut
down the server, it announces that there is a leak, but follows up
with the message 'memory leak detected: 0 blocks freed, etc...' or
something unhelpful to that effect.

My questions:

1) Have other people on other OSs noted memory leak problems?

2) Has it been pinpointed to msqld, as opposed to a buggy malloc
library?

3) Any suggestions on how to pinpoint where the error might be?

My diagnostic skills do not extend to an application of this scope...