support for shared libraries in StackTrace

master
Marc Wäckerlin 20 years ago
parent f9d8a0f767
commit a48e58ce27
  1. 31
      NEWS

31
NEWS

@ -1,26 +1,5 @@
In release 1.0.0, some headers are missing in the rpm packages and in StackTrace now can load not only the executable, but also shared
the installation with make install. Don't use that release, use 1.1.0 libraries. On Linux, if StackTrace is initialized without parameters,
instead. then not only the executable is löoaded, but also /usr/bin/ldd is
executed on the executable and all shared libraries with their offset
Please note that the inheritance changed for the exception classes: are parsed from the output and loaded.
There is no more a diamond like multiple inheritance nos, but
exceptions such as mrw::out_of_range no more inherit from their
std::out_of_range correspondant. All exceptions still inherit from
mrw::exception which inherits from std::exception.
New feature: C++ standard extensions. It provides some features that
are missing in the C++ standard, such as shift operator for string and
container.
The naming of libraries was not intuitive before, e.g. the library
from mrw-c++-0.93 was named libmrw.so.0.0.93 instead of
libmrw.so.0.93.0 and release mrw-c++-1.5 would have been named
libmrw.so.1.0.5. That's a problem with the unconventional version
naming in the libtool. The naming in libtool may make sense only, if
you have several completely independent libraries in the same
package. Now the naming is as it should be, the package and the
library have three digits, increasing the least means no change in
behaviour, e.g. little bugfix, increasing the middle means more
features, but the interface remains backward compatible and increasing
the first number means, that the interface has broken backwards
compatibility, i.e. features have been removed.

Loading…
Cancel
Save