libunwind-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libunwind-devel] Status of "libunwind" on HPUX/IA64


From: David Mosberger-Tang
Subject: Re: [Libunwind-devel] Status of "libunwind" on HPUX/IA64
Date: Mon, 7 Nov 2011 10:45:29 -0700

Volker,

I don't think anybody every seriously pursued libunwind on HP-UX since HP-UX already had a processor-specific unwind API.  I just did some basic work to verify that libunwind could work in principle on HP-UX.  It's a fair amount of work to properly validate an unwind library on IA-64, so if you can live with a processor-specific API, you might be better off with Unwind or Unwind Express.

Having said that, the IA-64 tests in libunwind are quite extensive and if you could "make check" to pass (mostly) you'd probably be in good shape.

I haven't worked on IA-64 in several years, but I still have an Itanium box, so I might be able to at least help make sure the current libunwind works properly on IA-64 Linux.

  --david

On Mon, Nov 7, 2011 at 9:12 AM, Volker Simonis <address@hidden> wrote:
Hi David,

back in 2006, you advised to better not use libunwind on HPUX/IA64:

http://lists.nongnu.org/archive/html/libunwind-devel/2006-04/msg00001.html

Now I saw in the current README file that the implementation on
HPUX/IA64 "Mostly works but [is] known to have some serious
limitations."

What are these "serious limitations"?
Is there any documentation where we can find out more about the
limitations on HPUX?

If you would have to unwind mixed native(i.e. C/C++)/Java(i.e.
JITed/interpreted frames) on HPUX/IA64 today, would you advise to use

1. vanilla libunwind
2. Unwind Express Library
(http://docstore.mik.ua/manuals/hp-ux/en/B2355-60130/uwx.3X.html)
3. Unwind Library
(http://docstore.mik.ua/manuals/hp-ux/en/B2355-60130/unwind.5.html)

Thank you in advance and best regards,
Volker



--
eGauge Systems LLC, http://egauge.net/, 1.877-EGAUGE1, fax 720.545.9768

reply via email to

[Prev in Thread] Current Thread [Next in Thread]