From: ratheesh k <ratheesh.ksz@gmail.com>
To: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: print user stack
Date: Sat, 23 Oct 2010 20:01:19 +0530 [thread overview]
Message-ID: <AANLkTi=5Odw1sOWqXLD1Kxg4c-evTNt-dWzyxQUNFGix@mail.gmail.com> (raw)
In-Reply-To: <20101023132629.GC3163@uudg.org>
On Sat, Oct 23, 2010 at 6:56 PM, Luis Claudio R. Goncalves
<lclaudio@uudg.org> wrote:
>but have you verified your core file size limit
>(ulimit -c)?
Yes. it is unlimited.
-Ratheesh
> On Sat, Oct 23, 2010 at 05:46:35PM +0530, ratheesh k wrote:
> | I had a strange problem of core file getting truncated. I could not
> | find any stack trace.
> |
> |
> | So, i wrote a kernel module. Which will find a task_struct using pid.
> | find_task_jby_pid.
> | then i used show_stack for the same task struct to list out the stack
> | trace. But it is printing the kernel stack not user stack. Any idea
> | how to print user stack .
>
> Sorry if that sounds silly, but have you verified your core file size limit
> (ulimit -c)?
>
> About printing the user stack from whithin the kernel, I understand the
> utrace folks were working on that.
>
> Cheers,
> Luis
>
>
> --
> [ Luis Claudio R. Goncalves Bass - Gospel - RT ]
> [ Fingerprint: 4FDD B8C4 3C59 34BD 8BE9 2696 7203 D980 A448 C8F8 ]
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-10-23 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 12:16 print user stack ratheesh k
2010-10-23 13:18 ` RT scheduling / scheduling of RT groups Armin Steinhoff
2010-10-24 10:12 ` Armin Steinhoff
2010-10-25 19:37 ` Xianghua Xiao
2010-10-23 13:26 ` print user stack Luis Claudio R. Goncalves
2010-10-23 14:31 ` ratheesh k [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=5Odw1sOWqXLD1Kxg4c-evTNt-dWzyxQUNFGix@mail.gmail.com' \
--to=ratheesh.ksz@gmail.com \
--cc=lclaudio@uudg.org \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).