From: Suparna Bhattacharya <suparna@in.ibm.com>
To: sathish jayapalan <sathish_jayapalan@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to crash a system and take a dump?
Date: Mon, 04 Feb 2002 19:02:52 +0530 [thread overview]
Message-ID: <3C5E8D84.5216D0EC@in.ibm.com> (raw)
In-Reply-To: <20020204112621.31480.qmail@web14805.mail.yahoo.com>
With LKCD, you can also trigger a dump via the Alt+Sysrq+c key.
If you run into problems when trying to use this, then you might need
some of the fixes that we've checked into the lkcd cvs tree.
Regards
Suparna
IBM Linux Technology Center
sathish jayapalan wrote:
>
> Hi,
> I have a doubt. I know that linux kernel doesn't crash
> so easily. Is there any way to panic the system? Can I
> go to the source area and insert/modify a variable in
> kernel code so that the kernel references a null
> pointer and crashes while running the kernel compiled
> with this variable. My aim is to learn crash dump
> analysis with 'Lcrash tool". Please help me out with
> this.
>
> Thanks in advance,
> sathish
>
> __________________________________________________
> Do You Yahoo!?
> Great stuff seeking new owners in Yahoo! Auctions!
> http://auctions.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-02-04 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 11:26 How to crash a system and take a dump? sathish jayapalan
2002-02-04 12:31 ` Gianni Tedesco
2002-02-04 13:32 ` Suparna Bhattacharya [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-04 11:40 Alexander Sandler
2002-02-05 2:32 ` Philippe Troin
2002-02-05 18:50 Alexander Sandler
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=3C5E8D84.5216D0EC@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sathish_jayapalan@yahoo.com \
/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