[prev in list] [next in list] [prev in thread] [next in thread]
List: elinks-cvs
Subject: [ELinks] elinks - pasky: Move backtrace printing support enabling ...
From: cvs () pasky ! ji ! cz
Date: 2003-12-31 22:01:29
Message-ID: 20031231220129.9903.qmail () machine ! sinus ! cz
[Download RAW message or body]
This is an automated notification of a change to the ELinks CVS tree.
Author: pasky
Module: elinks
Tag: <TRUNK>
Date: Wed Dec 31 22:01:29 2003 GMT
---- Log message:
Move backtrace printing support enabling to feature.h.
---- Files affected:
elinks:
acconfig.h (1.66 -> 1.67)
http://cvsweb.elinks.or.cz/cvsweb.cgi/elinks/acconfig.h.diff?r1=1.66&r2=1.67&f=u
configure.in (1.324 -> 1.325)
http://cvsweb.elinks.or.cz/cvsweb.cgi/elinks/configure.in.diff?r1=1.324&r2=1.325&f=u
feature.h (1.6 -> 1.7)
http://cvsweb.elinks.or.cz/cvsweb.cgi/elinks/feature.h.diff?r1=1.6&r2=1.7&f=u
---- Diffs:
Index: elinks/acconfig.h
diff -u elinks/acconfig.h:1.66 elinks/acconfig.h:1.67
--- elinks/acconfig.h:1.66 Wed Dec 31 22:31:49 2003
+++ elinks/acconfig.h Wed Dec 31 23:01:24 2003
@@ -81,10 +81,6 @@
/* Force use of internal functions instead of those of system libc */
#undef USE_OWN_LIBC
-/* Define to 1 if we should include a generic backtrace printing infrastructure */
-/* (you will still need some support from the libc) */
-#undef BACKTRACE
-
/* Enable forms memory */
#undef FORMS_MEMORY
Index: elinks/configure.in
diff -u elinks/configure.in:1.324 elinks/configure.in:1.325
--- elinks/configure.in:1.324 Wed Dec 31 22:31:49 2003
+++ elinks/configure.in Wed Dec 31 23:01:24 2003
@@ -782,31 +782,10 @@
dnl Backtraces displaying support.
dnl ===================================================================
-hm_enabled_backtrace="yes"
-hm_forced_backtrace="no"
-
-AC_ARG_ENABLE(backtrace, [ --disable-backtrace disable displaying of backtrace upon crash],
- [if test "$enableval" = yes; then
- hm_forced_backtrace="yes"
- else
- hm_enabled_backtrace="no"
- fi])
-
-AC_MSG_CHECKING(for backtrace displaying support)
-
-if test "x$hm_enabled_backtrace" = "xyes"; then
- AC_MSG_RESULT(enabled)
- AC_CHECK_HEADERS(execinfo.h, have_execinfo=yes, have_execinfo=no)
- # possible checks for other system-specific means go here
- if test "$have_execinfo" = yes; then
- AC_DEFINE(BACKTRACE)
- else
- if test "x$hm_forced_backtrace" = "xyes"; then
- AC_MSG_ERROR(No backtrace listing system capability found.)
- fi
- fi
-else
- AC_MSG_RESULT(no)
+AC_CHECK_HEADERS(execinfo.h, have_execinfo=yes, have_execinfo=no)
+# possible checks for other system-specific means go here
+if test "$have_execinfo" = yes; then
+ AC_DEFINE(BACKTRACE)
fi
Index: elinks/feature.h
diff -u elinks/feature.h:1.6 elinks/feature.h:1.7
--- elinks/feature.h:1.6 Wed Dec 31 22:52:31 2003
+++ elinks/feature.h Wed Dec 31 23:01:24 2003
@@ -191,4 +191,29 @@
/* #define USE_256_COLORS */
+/*** Backtrace printing
+ *
+ * Once upon a time, a disaster happens and ELinks crashes. That is a very sad
+ * event and it would be very nice to have some means how to diagnose it. In
+ * the crash handler, ELinks prints out various helpful things, however the
+ * truly important information is _where_ did it crash. Usually, users do not
+ * have gdb installed and can't provide a backtrace. However, ELinks can print
+ * a backtrace on its own, if the system supports it (currently, it is
+ * implemented only for glibc). It is not always accurate, it is useless when
+ * the ELinks binary is stripped and it still misses a lot of important
+ * information, but it can be sometimes still an indispensable help for the
+ * developers.
+ *
+ * You should keep this, unless you will strip your ELinks binary anyway, you
+ * know you are not going to report back any failures and you care about each
+ * single wasted bit.
+ *
+ * Default: enabled if the libc supports it (only glibc) */
+
+#ifdef BACKTRACE
+/* Comment out the following line if you want to always have this disabled: */
+#undef BACKTRACE
+#endif
+
+
#endif
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic