public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Greg Ungerer <gerg@snapgear.com>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	gerg@uclinux.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68knommu: add pretty back strace
Date: Fri, 02 May 2008 20:27:57 +0100	[thread overview]
Message-ID: <481B6B3D.9060200@grupopie.com> (raw)
In-Reply-To: <200805010216.m412GcUQ004101@goober>

Greg Ungerer wrote:
> From: Sebastian Siewior <bigeasy@linutronix.de>
> 
> With this patch and
>  CONFIG_FRAME_POINTER=y
>  CONFIG_KALLSYMS=y
> The backtrace shows resolved function names and their numeric
> address.

This is really not my area, but this patch reminds me of all the dwarf2 
unwinder on x86 that caused so many problems in the beginning...

> [...]
> +#ifdef CONFIG_FRAME_POINTER
> +	printk(KERN_EMERG "Call Trace:\n");
> +
> +	last_stack = stack - 1;
> +	while (stack <= endstack && stack > last_stack) {
> +
> +		addr = *(stack + 1);
> +		printk(KERN_EMERG " [%08lx] ", addr);
> +		print_symbol(KERN_CONT "%s\n", addr);
> +
> +		last_stack = stack;
> +		stack = (unsigned long *)*stack;
>  	}
>  	printk("\n");
> +#else
> +	printk(KERN_EMERG "CONFIG_FRAME_POINTER disabled, no symbolic call trace\n");

You could probably fall back to the old method in this case, no?

Also, if the stack is slightly corrupted on the top, the new method 
might just bail out without giving any indication about the path that 
lead there, when instead it could also fall back to the old method.

-- 
Paulo Marques - www.grupopie.com

"Feed the hungry, save the whales, free the mallocs!"

  reply	other threads:[~2008-05-02 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01  2:16 [PATCH] m68knommu: add pretty back strace Greg Ungerer
2008-05-02 19:27 ` Paulo Marques [this message]
2008-05-02 21:10   ` Sebastian Siewior
2008-05-05 19:21     ` Paulo Marques
2008-05-06  4:52       ` Greg Ungerer

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=481B6B3D.9060200@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=akpm@linux-foundation.org \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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