From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: Why is it so difficult to get a Lisp backtrace? Date: Sat, 25 Jun 2022 17:30:30 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29552"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Emacs developers To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 25 17:33:11 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o57mZ-0007W2-Ep for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jun 2022 17:33:11 +0200 Original-Received: from localhost ([::1]:33798 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o57mY-0007eV-Ee for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jun 2022 11:33:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57168) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o57kJ-000678-SN for emacs-devel@gnu.org; Sat, 25 Jun 2022 11:30:51 -0400 Original-Received: from mail-pg1-f172.google.com ([209.85.215.172]:33689) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o57kH-0006f3-JQ for emacs-devel@gnu.org; Sat, 25 Jun 2022 11:30:51 -0400 Original-Received: by mail-pg1-f172.google.com with SMTP id z14so5136885pgh.0 for ; Sat, 25 Jun 2022 08:30:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rMYA759du/e2qCaMeaIhNxcYtVeOQnwOyJ4vpyLceZc=; b=GL3G4ECDT4lVGI6z1EXiVS7JEwS7rgGi1GY+NiTZEIF0ebRHn28ekWPWRmUTT4xA4x 7LZB6DgvLBw1qX6apfm8RVPmri90XiqJQKMx1MQbRMA2SsZT6tt3elKZvAh4Y3auCm0n PbNrxHHdSWs/V7JJCuaqgG9SX6DVEq/Iu3VSlsMkUWonylHBYVIV8s1vnTmyDmBcm+qf 3m2/CJjlXFGUEBARielg3Ikq/a1tdA292nKkEMkdOcXV3F3AveLAqIbWpL4LQla+miIM tTVIWI8F3Tfdd6psa8FoGKopQazqA2tqU0ZJSFpHW9ynZMFLjQVEmxARLoFeWcZ0zLng yEww== X-Gm-Message-State: AJIora+o3Anc2dygNNEN+qpxJn6CxL5DXU/wsURFyC/I2CxglSCZkYWS i6ozhx1/RN6LBJerjsyy/9bvEm5eSMqe77bRNg5I1CJJ X-Google-Smtp-Source: AGRyM1sdYWemrudq7FR6+CGekF+lI+K0L+32ENN4SEok1q4ZYjNY5gnHdbx7Dhg0zgJYEkmj7uMDzrmTRYqlounonSI= X-Received: by 2002:a63:ed48:0:b0:40d:9866:6834 with SMTP id m8-20020a63ed48000000b0040d98666834mr4004541pgk.324.1656171041574; Sat, 25 Jun 2022 08:30:41 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=209.85.215.172; envelope-from=stefankangas@gmail.com; helo=mail-pg1-f172.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291612 Archived-At: Alan Mackenzie writes: > I mean something like the following, which to a first approximation, > works. To use it, do M-x debug-next-command and the execute the command > expected to give errors: Good idea, but how about just making it into a manual toggle? I might need to run more than one command to reproduce a bug.