Yes, removing libc.so.1
Output ! - now to analyze the output I will bring in my parallel
mailman-users' thread folks :) - having the stack trace is awesome by
itself...
thanks
0 42246 realloc:return Ptr=0x824c268 Oldptr=0x0 Size=16
libc.so.1`realloc+0x33a
python`addcleanup+0x45
python`convertsimple+0x145d
python`vgetargs1+0x259
python`_PyArg_ParseTuple_SizeT+0x1d
python`posix_listdir+0x55
python`PyEval_EvalFrameEx+0x59ff
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalFrameEx+0x49ff
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalCode+0x22
python`PyRun_FileExFlags+0xaf
python`PyRun_SimpleFileExFlags+0x156
python`Py_Main+0xa6b
python`main+0x17
python`_start+0x80
0 42249 free:entry Ptr=0x824c268
0 42244 lmalloc:return Ptr=0xcf890300 Size=16
libc.so.1`lmalloc+0x143
libc.so.1`opendir+0x3e
python`posix_listdir+0x6d
python`PyEval_EvalFrameEx+0x59ff
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalFrameEx+0x49ff
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalCode+0x22
python`PyRun_FileExFlags+0xaf
python`PyRun_SimpleFileExFlags+0x156
python`Py_Main+0xa6b
python`main+0x17
python`_start+0x80
0 42244 lmalloc:return Ptr=0xcf894000 Size=8192
libc.so.1`lmalloc+0x143
libc.so.1`opendir+0x3e
python`posix_listdir+0x6d
python`PyEval_EvalFrameEx+0x59ff
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalFrameEx+0x49ff
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalCode+0x22
python`PyRun_FileExFlags+0xaf
python`PyRun_SimpleFileExFlags+0x156
python`Py_Main+0xa6b
python`main+0x17
python`_start+0x80
0 42249 free:entry Ptr=0x86d78f0
^C
0 42246 realloc:return Ptr=0x824c268 Oldptr=0x0 Size=16
libc.so.1`realloc+0x33a
python`addcleanup+0x45
python`convertsimple+0x145d
python`vgetargs1+0x259
python`_PyArg_ParseTuple_SizeT+0x1d
python`posix_listdir+0x55
python`PyEval_EvalFrameEx+0x59ff
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalFrameEx+0x49ff
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalCode+0x22
python`PyRun_FileExFlags+0xaf
python`PyRun_SimpleFileExFlags+0x156
python`Py_Main+0xa6b
python`main+0x17
python`_start+0x80
0 42249 free:entry Ptr=0x824c268
0 42244 lmalloc:return Ptr=0xcf890300 Size=16
libc.so.1`lmalloc+0x143
libc.so.1`opendir+0x3e
python`posix_listdir+0x6d
python`PyEval_EvalFrameEx+0x59ff
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalFrameEx+0x49ff
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalCode+0x22
python`PyRun_FileExFlags+0xaf
python`PyRun_SimpleFileExFlags+0x156
python`Py_Main+0xa6b
python`main+0x17
python`_start+0x80
0 42244 lmalloc:return Ptr=0xcf894000 Size=8192
libc.so.1`lmalloc+0x143
libc.so.1`opendir+0x3e
python`posix_listdir+0x6d
python`PyEval_EvalFrameEx+0x59ff
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalFrameEx+0x49ff
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalCode+0x22
python`PyRun_FileExFlags+0xaf
python`PyRun_SimpleFileExFlags+0x156
python`Py_Main+0xa6b
python`main+0x17
python`_start+0x80
0 42249 free:entry Ptr=0x86d78f0
On 7/2/08 7:46 AM, "rickey c weisner" <[EMAIL PROTECTED]> wrote:
> Fletcher,
> This looks suspicious. Perhaps your malloc is not in libc ?
>> [690] | 0| 0|FILE |LOCL |0 |ABS |obmalloc.c
> remove the libc.so.1 from your probe description.
> rick
>
> On Wed, Jul 02, 2008 at 07:23:49AM -0700, Fletcher Cocquyt wrote:
>> Date: Wed, 02 Jul 2008 07:23:49 -0700
>> From: Fletcher Cocquyt <[EMAIL PROTECTED]>
>> Subject: Re: [dtrace-discuss] Memory leak scripts
>> In-reply-to: <[EMAIL PROTECTED]>
>> To: rickey c weisner <[EMAIL PROTECTED]>
>> Cc: [email protected]
>> Thread-topic: [dtrace-discuss] Memory leak scripts
>> Thread-index: AcjcTz6M0DPfSSwvAEuYeh4RTBFiig==
>> X-PMX-Version: 5.4.1.325704
>> X-Brightmail-Tracker: AAAAAA==
>> X-Antispam: No, score=0.0/5.0, scanned in 0.102sec at (localhost [127.0.0.1])
>> by smf-spamd v1.3.1 - http://smfs.sf.net/
>> User-Agent: Microsoft-Entourage/12.11.0.080522
>> Original-recipient: rfc822;[EMAIL PROTECTED]
>>
>> Looks OK:
>>
>> [EMAIL PROTECTED]:~ 7:22am 60 # !nm
>> nm /bin/python | egrep malloc
>> [3597] | 134599012| 0|FUNC |GLOB |0 |UNDEF |malloc
>>
>>
>>
>> On 7/2/08 6:11 AM, "rickey c weisner" <[EMAIL PROTECTED]> wrote:
>>
>>> Fletcher,
>>> First confirm that malloc is in your binary.
>>>
>>> arwen:nm a.out | grep malloc
>>> [70] | 134547228| 0|FUNC |GLOB |0 |UNDEF |malloc
>>>
>>> Then key on any malloc.
>>> Something like:
>>> pid$target::malloc:return,
>>> pid$target::memalign:return,
>>> pid$target::realloc:return,
>>> pid$target::valloc:return
>>>
>>> rick
>>
>> --
>> Fletcher Cocquyt
>> Senior Systems Administrator
>> Information Resources and Technology (IRT)
>> Stanford University School of Medicine
>>
>> Email: [EMAIL PROTECTED]
>> Phone: (650) 724-7485
>>
>>
--
Fletcher Cocquyt
Senior Systems Administrator
Information Resources and Technology (IRT)
Stanford University School of Medicine
Email: [EMAIL PROTECTED]
Phone: (650) 724-7485
_______________________________________________
dtrace-discuss mailing list
[email protected]
