From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Enabling --enable-check-lisp-object-type by default on x86 and AMD64 Date: Wed, 03 May 2017 21:22:09 +0300 Message-ID: <83efw5hkby.fsf@gnu.org> References: <83mvb8riq0.fsf@gnu.org> <83a878r2d0.fsf@gnu.org> <60379b71-bd6a-5f6f-dec1-523d6f4b2016@cs.ucla.edu> <83vapihdgs.fsf@gnu.org> <83shkmgfnh.fsf@gnu.org> <777fd9a2-232a-e52c-0a51-3d287567fb2e@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1493835798 19233 195.159.176.226 (3 May 2017 18:23:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 3 May 2017 18:23:18 +0000 (UTC) Cc: p.stephani2@gmail.com, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 03 20:23:11 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d5yvd-0004oT-EU for ged-emacs-devel@m.gmane.org; Wed, 03 May 2017 20:23:09 +0200 Original-Received: from localhost ([::1]:38108 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5yvj-0000Hr-3X for ged-emacs-devel@m.gmane.org; Wed, 03 May 2017 14:23:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43249) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5yv9-0000Hj-He for emacs-devel@gnu.org; Wed, 03 May 2017 14:22:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d5yv5-0004mO-Jg for emacs-devel@gnu.org; Wed, 03 May 2017 14:22:39 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:51244) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5yv5-0004m9-H8; Wed, 03 May 2017 14:22:35 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4667 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1d5yv4-0002MI-AJ; Wed, 03 May 2017 14:22:35 -0400 In-reply-to: <777fd9a2-232a-e52c-0a51-3d287567fb2e@cs.ucla.edu> (message from Paul Eggert on Wed, 3 May 2017 11:08:23 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:214547 Archived-At: > Cc: p.stephani2@gmail.com, emacs-devel@gnu.org > From: Paul Eggert > Date: Wed, 3 May 2017 11:08:23 -0700 > > > Only partially. People who report backtraces seldom bother to start > > GDB from the Emacs's src directory, let alone source .gdbinit by hand. > > Moreover, latest versions of GDB refuse to auto-load .gdbinit files > > from random directories, unless you put some magic in your ~/.gdbinit > > (which most people don't). > > This problem is not new. It isn't new, but previously it only affected displaying Lisp data in human-readable form. Now it will also affect backtraces. > How about using GDB pretty-printers instead? This is better, but how sure we are people's GDB is built with Python support? > E.g., add something like the attached file as src/gdb-pretty.py, and > add the line "source gdb-pretty.py" to src/.gdbinit. Why not make this part of .gdbinit itself?