public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bs@q-leap.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: frame unwinder patches
Date: Fri, 5 Sep 2008 11:19:21 +0200	[thread overview]
Message-ID: <200809051119.21699.bs@q-leap.de> (raw)
In-Reply-To: <20080904102936.28e10c39@infradead.org>

On Thursday 04 September 2008 19:29:36 Arjan van de Ven wrote:
> On Thu, 04 Sep 2008 18:46:52 +0200
>
> Bernd Schubert <bs@q-leap.de> wrote:
> > Hello,
> >
> > up to 2.6.22 the -mm series had these nice frame unwinder patches,
> > which gave beautiful stack traces. Unfortunately these frame unwinder
> > patches seem to have been dropped :(
> >
> > Anyone still maintaining updated patches?
> >
> > Probably all the "?" lines shouldn't be printed.
>
> printing the ? lines is the result of a compromise between getting the
> most reliable information out of a stack trace, and getting a useful
> data for the case where not everything is going as well as it should.
>
> not printing the ? would be trivial (for some backtraces we do that),
> but so far hasn't been seen as desirable because you lose information
> in those hard-to-debug cases when you need anything you can get from
> the backtrace.

I see your point, but in most cases it is rather annoying.


Bernd

-- 
Bernd Schubert
Q-Leap Networks GmbH

  reply	other threads:[~2008-09-05  9:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 16:46 frame unwinder patches Bernd Schubert
2008-09-04 17:29 ` Arjan van de Ven
2008-09-05  9:19   ` Bernd Schubert [this message]
2008-09-05 13:33     ` Arjan van de Ven
2008-09-05 13:52       ` Bernd Schubert
2008-09-05 14:13         ` Arjan van de Ven
2008-09-05 14:48           ` Bernd Schubert
2008-09-05 14:57             ` Arjan van de Ven
2008-09-05 15:08               ` Andi Kleen
2008-09-04 19:13 ` Andi Kleen
2008-09-05  9:24   ` Bernd Schubert
2008-09-05  9:43     ` Andi Kleen

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=200809051119.21699.bs@q-leap.de \
    --to=bs@q-leap.de \
    --cc=arjan@infradead.org \
    --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