All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hoeflinger, Jay P" <jay.p.hoeflinger@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] ias and stack unwind
Date: Fri, 11 Apr 2003 21:55:15 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705480@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705471@msgid-missing>

I don't think that explains it in my case.  I'm using ecc version 7.1.
Did you have to use any special options?  

Jay

-----Original Message-----
From: David Mosberger [mailto:davidm@napali.hpl.hp.com]
Sent: Friday, April 11, 2003 4:06 PM
To: Hoeflinger, Jay P
Cc: linux-ia64@linuxia64.org
Subject: Re: [Linux-ia64] ias and stack unwind


>>>>> On Fri, 11 Apr 2003 12:05:30 -0700, "Hoeflinger, Jay P" <jay.p.hoeflinger@intel.com> said:

  Jay> Has anyone had any problems with the stack unwind directives and ias?
  Jay> For some reason when I put the unwind directives in my assembler code,
  Jay> then do a "readelf -u", it says that the assembly routine has version 2
  Jay> unwind info and can't list it.  libunwind seems to have similar problems
  Jay> and can't unwind from the assembly routine.  For all the C routines in
  Jay> the program, the unwind info version is 1, as the IA64 Software Conventions
  Jay> and Runtime Architecture Guide indicates it should be.

  Jay> Any pointers for getting ias to use version 1 would be appreciated.

Recently, I have tested libunwind (and readelf -u) with Intel ECC v7.0
and it worked fine.  I'm told earlier versions may have generated bad
(incompatible) unwind info, but I haven't verified that myself.  Could
this explain it?

	--david


  parent reply	other threads:[~2003-04-11 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 19:05 [Linux-ia64] ias and stack unwind Hoeflinger, Jay P
2003-04-11 21:06 ` David Mosberger
2003-04-11 21:55 ` Hoeflinger, Jay P [this message]
2003-04-11 22:02 ` David Mosberger

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=marc-linux-ia64-105590723705480@msgid-missing \
    --to=jay.p.hoeflinger@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.