From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Christopher Allan Webber Newsgroups: gmane.lisp.guile.user Subject: Re: Stack traces Date: Wed, 15 Feb 2017 09:36:33 -0600 Message-ID: <87mvdn4gam.fsf@dustycloud.org> References: <87h93wto3y.fsf_-_@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1487173041 30222 195.159.176.226 (15 Feb 2017 15:37:21 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 15 Feb 2017 15:37:21 +0000 (UTC) User-Agent: mu4e 0.9.18; emacs 25.1.1 Cc: guile-user@gnu.org To: Ludovic =?utf-8?Q?Court=C3=A8s?= Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Wed Feb 15 16:37:17 2017 Return-path: Envelope-to: guile-user@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 1ce1ds-0007Tp-Qq for guile-user@m.gmane.org; Wed, 15 Feb 2017 16:37:16 +0100 Original-Received: from localhost ([::1]:41398 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ce1dy-0008Ee-9y for guile-user@m.gmane.org; Wed, 15 Feb 2017 10:37:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53578) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ce1dI-00089W-4F for guile-user@gnu.org; Wed, 15 Feb 2017 10:36:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ce1dD-0002pL-7X for guile-user@gnu.org; Wed, 15 Feb 2017 10:36:40 -0500 Original-Received: from dustycloud.org ([50.116.34.160]:36452) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ce1dD-0002oY-2E; Wed, 15 Feb 2017 10:36:35 -0500 Original-Received: from oolong (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id 9BA032665F; Wed, 15 Feb 2017 10:36:33 -0500 (EST) In-reply-to: <87h93wto3y.fsf_-_@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 50.116.34.160 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: "guile-user" Xref: news.gmane.org gmane.lisp.guile.user:13229 Archived-At: Ludovic Court=C3=A8s writes: > Hello, > > Cecil McGregor skribis: > >> My first problem lies in the lack of a decent debugger. >> (I can hear the screams of more enlightened Guilers >> already!) The stack traces seldom provide filenames >> and line numbers to hint where a problem might hide. >> While I've read advice to allow the appearance of >> filenames/line numbers, I still can't seem to >> consistently find these in a stack trace. >> >> I would really like the filename/line number to appear >> in a stack trace with the actual source code and not >> some partially opaque macro expansion. > > Could you mock up the stack trace as you would like to see it displayed= ? > > I think it would be helpful because what you write here is a common > complaint, but it=E2=80=99s also something that seasoned Guilers no lon= ger > realize because they=E2=80=99re used to it. So a fresh eye on what it = should > look like is great. > > There are also deeper technical issues, such as tail calls, but we can > put them aside for now. > > Thanks, > Ludo=E2=80=99. One thing that we see requested a lot is how to do the equivalent of: import pdb pdb.set_trace() in python, just dumping something to "trigger" the debugger somewhere. I seem to remember getting some arcane code to do something similar, but maybe we can just have a simple invocation that people could put anywhere. (Amirouche has been raising this one also I think.)