public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "George Krajcsovits" <george.krajcsovits@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Callchain contains impossible call
Date: 01 Jun 2007 13:32:07 +0200	[thread overview]
Message-ID: <p73wsync3m0.fsf@bingen.suse.de> (raw)
In-Reply-To: <42c83d030706010019u13219322o7cec0c7aa08dd01f@mail.gmail.com>

"George Krajcsovits" <george.krajcsovits@gmail.com> writes:

> this is probably RTFM (where is this manual?), but how did I get a
> callchain on a uniprocessor
> system where there are two functions that cannot be a part of it,
> because they don't call anything ? (kfree_skbmem and __kmalloc). Also
> at the end one function call is there twice.

Linux stack traces are not exact by default.

-Andi

      parent reply	other threads:[~2007-06-01 10:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01  7:19 Callchain contains impossible call George Krajcsovits
2007-06-01  7:25 ` How to access kdb explicitly gshan
2007-06-01  8:42   ` Jiri Kosina
2007-06-01  8:44     ` gshan
2007-06-01 10:33 ` Callchain contains impossible call Miklos Szeredi
2007-06-01 11:32 ` Andi Kleen [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=p73wsync3m0.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=george.krajcsovits@gmail.com \
    --cc=linux-kernel@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