public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Simon Turvey <turveysp@ntlworld.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Generating a function call trace
Date: Fri, 30 Nov 2001 16:33:58 +0100	[thread overview]
Message-ID: <3C07A6E6.45A4AC61@evision-ventures.com> (raw)
In-Reply-To: <001501c179b1$870db7c0$140ba8c0@mistral>

Simon Turvey wrote:
> 
> Is it possible to arbitrarily generate (in a module say) a function call
> trace?
> 

Just insert the dereference of a NULL pointer where you wan't to have
it.
The oops gives you what you wan't....
Or better attach the gdb to /proc/kmem (you will have to compile the
kernel with
debugging on in front of this action) and have fun.

  reply	other threads:[~2001-11-30 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30 15:13 Generating a function call trace Simon Turvey
2001-11-30 15:33 ` Martin Dalecki [this message]
2001-11-30 16:19   ` Petr Vandrovec
2001-11-30 17:02 ` Davide Libenzi
2001-11-30 18:20   ` Brian Gerst
2001-11-30 18:39     ` Davide Libenzi
2001-11-30 18:37       ` Martin Dalecki
2001-12-01 19:00     ` Matt D. Robinson

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=3C07A6E6.45A4AC61@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=dalecki@evision.ag \
    --cc=linux-kernel@vger.kernel.org \
    --cc=turveysp@ntlworld.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