Re: PATCH m68knommu clear frame-pointer in start_thread

On Wed, Mar 15, 2006 at 05:47:07PM +0100, Philippe De Muyter wrote:

> When trying to print the calltrace of a user process on m68knommu targets
> gdb follows the frame-pointer en falls on unreachable adresses, because
> the frame pointer is not properly initialised by start_thread. This patch
> initialises the frame pointer to NULL in start_thread.
> 
> Signed-off-by: Philippe De Muyter <[email protected]>

You've posted an ed-style diff.  Quite a safe method to make sure nobody
will read it.  Pleae repost a unified diff.

  Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: PATCH m68knommu clear frame-pointer in start_thread
    • From: Philippe De Muyter <[email protected]>

• References:
  • PATCH m68knommu clear frame-pointer in start_thread
    • From: "Philippe De Muyter" <[email protected]>

• Prev by Date: Fix gus_pcm dereference before NULL
• Next by Date: Re: [PATCH 10 of 20] ipath - support for userspace apps using core driver
• Previous by thread: PATCH m68knommu clear frame-pointer in start_thread
• Next by thread: Re: PATCH m68knommu clear frame-pointer in start_thread
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]