linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lauraa@codeaurora.org (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add user_debug command line option
Date: Wed, 09 Apr 2014 11:11:06 -0700	[thread overview]
Message-ID: <53458D3A.8080806@codeaurora.org> (raw)
In-Reply-To: <20140409084101.GC13737@arm.com>

On 4/9/2014 1:41 AM, Catalin Marinas wrote:
> On Wed, Apr 09, 2014 at 02:45:08AM +0100, Laura Abbott wrote:
>> arm had a useful command line option to print out debug
>> information on user signals. This is somewhat like a more verbose
>> version of show_unhandled_signals. Add the user_debug command line
>> option to print out more information in a similar manner to
>> arm.
> 
> Is this because you want to print information for handled signals as
> well? What is the use case? (there are alternatives like ptrace as
> well).
> 

Yes. We've found user_debug to be helpful in correlating userspace
crashes to other events that are spewed in the system log. Example
from last week: userspace program crashes, bad page state and panic
happens soon after. Some kernel driver was not cleaning up after
itself properly after the crash. Without seeing the userspace crash
logs it would have been much more difficult to correlate the bad
page state to anything.

Laura

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

      reply	other threads:[~2014-04-09 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09  1:45 [PATCH] arm64: Add user_debug command line option Laura Abbott
2014-04-09  8:41 ` Catalin Marinas
2014-04-09 18:11   ` Laura Abbott [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=53458D3A.8080806@codeaurora.org \
    --to=lauraa@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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).