summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorhp.com!davidm <hp.com!davidm>2004-11-16 22:03:04 +0000
committerhp.com!davidm <hp.com!davidm>2004-11-16 22:03:04 +0000
commit0d34dce56ae66b8bec58f098c2a94783fc4de2e0 (patch)
treea9f16bf088eb1248ae87fcaece2e30880834e9a1 /NEWS
parent272caabbfae28e542c4c6b30f1c558a8e5fd748b (diff)
downloadlibunwind-0d34dce56ae66b8bec58f098c2a94783fc4de2e0.tar.gz
Update for v0.98.2 and v0.98.3 releases.
(Logical change 1.283)
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS25
1 files changed, 25 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 0292d97e..cedfa76b 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,30 @@
-*-Mode: outline-*-
+* News for v0.98.3:
+
+** Make it possible to link against libunwind-ia64.a only (i.e., without
+ requiring libunwind.a as well). This keeps apps which need only
+ remote unwinding cleaner, since they logically have no dependency
+ on libunwind.a.
+** Dont link against libatomic_ops for now. Due to a packaging bug on
+ Debian, linking against this library causes libunwind.so to get
+ a dependency on libatomic_ops.so, which is not at all what we want.
+ Fortunately, we don't have to link against that library on x86 or
+ ia64 since the library is strictly needed only for platforms with
+ poor atomic operation support. Once the libatomic_ops package is fixed,
+ we can re-enable linking against libatomic_ops.
+
+* News for v0.98.2:
+
+** Fixed bug which caused _UPT_get_dyn_info_list_addr() to sometimes fail
+ needlessly. Found by Todd L. Miller.
+
+** When using GCC to build libunwind on ia64, libunwind.so had an
+ unresolved reference to __divdi3. This is undesirable since it
+ creates an implicit dependency on libgcc. This problem has been
+ fixed in the 0.98.2 release by explicitly linking against libgcc.a
+ when building libunwind.
+
* News for v0.98.1:
** Fixed a bug which caused "make install" to install libunwind-common.h.in