| Date | Tue, 10 Dec 2013 17:21:50 -0500 | From | Steven Rostedt <> | Subject | Re: process 'stuck' at exit. |
| |
On Tue, Dec 10, 2013 at 05:16:21PM -0500, Dave Jones wrote: > 46.GA6962@home.goodmis.org> > User-Agent: Mutt/1.5.21 (2010-09-15) > X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 > Sender: linux-kernel-owner@vger.kernel.org > Precedence: bulk > List-ID: <linux-kernel.vger.kernel.org> > X-Mailing-List: linux-kernel@vger.kernel.org > X-UID: 421684 > Content-Length: 1147 > Status: O > > On Tue, Dec 10, 2013 at 05:09:46PM -0500, Steven Rostedt wrote: > > > So you can do either: > > > > trace-cmd record -p function -l get_user_pages_fast --func-stack sleep 5 > > > > Which will trace the get_user_pages_fast and spit out a full call trace. > This gives me a 100M trace.dat, but trace show shows.. > > # tracer: nop > # > # entries-in-buffer/entries-written: 0/0 #P:4 > # > # _-----=> irqs-off > # / _----=> need-resched > # | / _---=> hardirq/softirq > # || / _--=> preempt-depth > # ||| / delay > # TASK-PID CPU# |||| TIMESTAMP FUNCTION > # | | | |||| | | > > and that's it.
Oh, if you use trace-cmd record. You need to do trace-cmd report.
The trace-cmd show, shows you what's in the trace file, which was for the "manual" version.
Sorry for the confusion.
-- Steve
> > > Or if you don't want to use trace-cmd, you can
|