From owner-freebsd-stable Thu May 9 10:25:28 2002 Delivered-To: freebsd-stable@freebsd.org Received: from newtrinity.default-network.net (newtrinity.default-network.net [62.159.128.162]) by hub.freebsd.org (Postfix) with ESMTP id 20ACE37B40A; Thu, 9 May 2002 10:25:21 -0700 (PDT) Received: from newtrinity.default-network.net (corex@localhost [127.0.0.1]) by newtrinity.default-network.net (8.12.3/8.12.3/DEFAULT-NETWORK.NET) with ESMTP id g49HPJ2l083024; Thu, 9 May 2002 19:25:19 +0200 (CEST) (envelope-from corex@newtrinity.default-network.net) Received: (from corex@localhost) by newtrinity.default-network.net (8.12.3/8.12.3/Submit) id g49HPHE2083023; Thu, 9 May 2002 19:25:17 +0200 (CEST) (envelope-from corex) Date: Thu, 9 May 2002 19:25:17 +0200 From: marius@alchemy.franken.de To: Gregory Neil Shapiro Cc: Mike Tancsa , stable@FreeBSD.ORG, sendmail-questions@sendmail.org Subject: Re: milter memory leak ? Message-ID: <20020509192517.C24010@newtrinity.default-network.net> References: <5.1.0.14.0.20020507024124.02f0e4d0@192.168.0.12> <15576.63.850937.404110@horsey.gshapiro.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <15576.63.850937.404110@horsey.gshapiro.net>; from gshapiro@FreeBSD.ORG on Tue, May 07, 2002 at 09:26:39AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, May 07, 2002 at 09:26:39AM -0700, Gregory Neil Shapiro wrote: > mike> Am I safe in assuming the sample milter in the documentation is free of > mike> error ? This is from > > No, I just found one. By the way, you should probably mail > sendmail-questions@sendmail.org for sendmail related questions, not > freebsd-stable. > could you please tell us the bug ? is there a known problem in the thread related stuff of libmilter or the pthread implementation of freebsd ? when i assemble a linked list of the recipients and finally try to put the list into a single string malloc()/realloc() fails at a certain point and the next function-call (regardless which funtion, also e.g. printf()) triggers a segfault. this happens when there are ~8-10 recipients, for less it works. a backtrace typically looks like this: Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libc_r.so.4...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x804a7f2 in mlfi_eom () (gdb) info threads * 1 process 69427 0x804a7f2 in mlfi_eom () (gdb) thread 1 [Switching to thread 1 (process 69427)] #0 0x804a7f2 in mlfi_eom () (gdb) bt #0 0x804a7f2 in mlfi_eom () #1 0x804dcf7 in st_bodyend () #2 0x804d39c in mi_engine () #3 0x804c1c1 in mi_handle_session () #4 0x804ba29 in mi_thread_handle_wrapper () #5 0x2808e477 in _thread_start () at /usr/data/bsd/fbsd/RELENG_4/src/lib/libc_r/uthread/uthread_create.c:322 #6 0x0 in ?? () this is with recent 4-stable and the uthread fixes from a few days ago and sendmail-8.12.3_1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message