This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug uprobes/7092] uprobes probes causing OOM
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 15 Dec 2008 19:39:09 -0000
- Subject: [Bug uprobes/7092] uprobes probes causing OOM
- References: <20081210190833.7092.dsmith@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2008-12-15 19:39 -------
(In reply to comment #0)
> Using the test cases from bug 7082 modified to use uprobes instead of
> uretprobes. Here are the testcases:
>
> [1]
> # stap -ve 'probe process("bash").function("*") {}' -w -c bash
> # exit [...]
> On a 16-way i386 system running kernel 2.6.18-125.el5PAE (beta RHEL5.3), with
> systemtap head, here are the test results:
>
> [1] OOM. When run, the machine gets an OOM in pass 5. The bash prompt is never
> seen. On the console, I see:
> [...]
Can you run a systemtap probe against this kernel to count the number of
utrace engine allocations? It could be that we are able to suck them up
at such a rate that we can exhaust free kernel memory.
See bug #7016 for some self-throttling logic we use elsewhere to limit
systemtap's impact on free kernel memory. We could have something similar
for uprobes attachment.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=7092
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.