unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: 13445@debbugs.gnu.org
Subject: bug#13445: add2rline usage in manual
Date: Sat, 19 Jan 2013 14:16:40 -0800	[thread overview]
Message-ID: <50FB1B48.3010008@cs.ucla.edu> (raw)
In-Reply-To: <9wvcazxq6y.fsf@fencepost.gnu.org>

With newer addr2line, -p is helpful because function names
aren't printed without it.  In trunk bzr 111564..5 I pushed the
following, to suggest -p if available and to say what to do with
older addr2line implementations.

=== modified file 'doc/emacs/ChangeLog'
--- doc/emacs/ChangeLog	2013-01-19 20:38:13 +0000
+++ doc/emacs/ChangeLog	2013-01-19 22:10:50 +0000
@@ -1,3 +1,10 @@
+2013-01-19  Paul Eggert  <eggert@cs.ucla.edu>
+
+	* trouble.texi (Crashing): Suggest -p for recent addrline.  (Bug#13445)
+	Without it, I don't see function names.  Older addrlines will die
+	out sooner or later, so tailor the suggestion to recent addrline
+	and put in a comment about older ones.
+
 2013-01-19  Glenn Morris  <rgm@gnu.org>
 
 	* custom.texi (Directory Variables): Fix paren typo.

=== modified file 'doc/emacs/trouble.texi'
--- doc/emacs/trouble.texi	2013-01-19 20:38:13 +0000
+++ doc/emacs/trouble.texi	2013-01-19 22:14:42 +0000
@@ -325,7 +325,8 @@
 
 @example
 sed -n 's/.*\[\(.*\)]$/\1/p' @var{backtrace} |
-  addr2line -C -f -i -e @var{bindir}/@var{emacs-binary}
+  addr2line -C -f -i -p -e @var{bindir}/@var{emacs-binary}
+# Omit '-p' for binutils 2.20 and earlier.
 @end example
 
 @noindent






  parent reply	other threads:[~2013-01-19 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15  0:09 bug#13445: add2rline usage in manual Glenn Morris
2013-01-15  8:58 ` Andreas Schwab
2013-01-19 22:16 ` Paul Eggert [this message]
2013-01-19 22:34   ` Glenn Morris
2013-01-19 22:50     ` Paul Eggert
2013-01-19 23:40       ` Glenn Morris

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50FB1B48.3010008@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=13445@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).