[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54770.1246392952@turing-police.cc.vt.edu>
Date: Tue, 30 Jun 2009 16:15:52 -0400
From: Valdis.Kletnieks@...edu
To: linux-kernel@...r.kernel.org
Cc: mm-commits@...r.kernel.org
Subject: Re: mmotm 2009-06-30-12-50 uploaded
On Tue, 30 Jun 2009 12:51:30 PDT, akpm@...ux-foundation.org said:
> The mm-of-the-moment snapshot 2009-06-30-12-50 has been uploaded to
This dies with quilt 0.44, thusly:
Applying patch procfs-provide-stack-information-for-threads-v08.patch
can't find file to patch at input line 20
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From: Stefani Seibold <stefani@...bold.net>
|
|A patch to give a better overview of the userland application stack usage,
|especially for embedded linux.
|
|Currently you are only able to dump the main process/thread stack usage
|which is showed in /proc/pid/status by the "VmStk" Value. But you get no
|information about the consumed stack memory of the the threads.
|
|There is an enhancement in the /proc/<pid>/{task/*,}/*maps and which marks
|the vm mapping where the thread stack pointer reside with "[thread stack
|xxxxxxxx]". xxxxxxxx is the maximum size of stack. This is a value
|information, because libpthread doesn't set the start of the stack to the
|top of the mapped area, depending of the pthread usage.
|
|A sample output of /proc/<pid>/task/<tid>/maps looks like:
|
|08048000-08049000 r-xp 00000000 03:00 8312 /opt/z
|08049000-0804a000 rw-p 00001000 03:00 8312 /opt/z
--------------------------
No file to patch. Skipping patch.
patch: **** /tmp/poPjWncl : No such file or directory
Patch procfs-provide-stack-information-for-threads-v08.patch does not apply (enforce with -f)
Yowza. Not sure what makes it think there's an issue at line 20, looks to
*me* like the actual patch starts on line 77.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists