public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Mosberger-Tang" <dmosberger@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: get back PT_IA_64_UNWIND program header
Date: Fri, 10 Aug 2007 01:58:52 +0000	[thread overview]
Message-ID: <ed5aea430708091858s352ed254p22cb7a7ae70209@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 504 bytes --]

I noticed that Ski was unable to do a stacktrace on the kernel.  Turns
out that's because the PT_IA_64_UNWIND program-header is missing.
Perhaps this is due to a change in binutils, but in any case, it seems
like we should be explicit about the unwind header, so this patch is
probably a good idea no matter what.  Note that the patch assumes that
the earlier patch to add a PT_NOTE header has been applied already.

Regards,

  --david
-- 
Mosberger Consulting LLC, http://www.mosberger-consulting.com/

[-- Attachment #2: pt_unwind.diff --]
[-- Type: text/plain, Size: 875 bytes --]

[IA64] Explicitly put the unwind section into its own program-header.  This
       used to be unnecessary (probably because binutils did it for us), but
       with current binutils (e.g., v2.17.50.20070804) we won't get
       the PT_IA_64_UNWIND header without this patch which will break
       unwinding in a debugger and simulators such as Ski.

Signed-off-by: David Mosberger-Tang <dmosberger@gmail.com>

--- arch/ia64/kernel/vmlinux.lds.S~	2007-08-09 11:38:28.000000000 -0600
+++ arch/ia64/kernel/vmlinux.lds.S	2007-08-09 19:40:08.000000000 -0600
@@ -21,6 +21,7 @@
   percpu PT_LOAD;
   data   PT_LOAD;
   note   PT_NOTE;
+  unwind 0x70000001; /* PT_IA_64_UNWIND, but ld doesn't match the name */
 }
 SECTIONS
 {
@@ -103,7 +104,8 @@
 	  __start_unwind = .;
 	  *(.IA_64.unwind*)
 	  __end_unwind = .;
-	}
+	} :code :unwind
+  code_continues2 : {} : code
 
   RODATA
 

                 reply	other threads:[~2007-08-10  1:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ed5aea430708091858s352ed254p22cb7a7ae70209@mail.gmail.com \
    --to=dmosberger@gmail.com \
    --cc=linux-ia64@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