all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: Davin Pearson <davin.pearson@gmail.com>, gnu.emacs.help@gnu.org
Subject: Re: Fwd: Fails to bring up a back trace
Date: Thu, 30 Nov 2023 11:17:02 +0100	[thread overview]
Message-ID: <ZWhhHp9intNqGtSi@tuxteam.de> (raw)
In-Reply-To: <9e93e315-10a9-46e0-ba8d-11d4d392d7ae@starynkevitch.net>

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

On Thu, Nov 30, 2023 at 10:47:36AM +0100, Basile Starynkevitch wrote:
> 
> On 11/30/23 05:58, tomas@tuxteam.de wrote:
> > On Thu, Nov 30, 2023 at 10:43:45AM +1300, Davin Pearson wrote:
> > 
> > [...]
> > 
> > > Yet it fails to bring up an error backtrace.
> > I fear this is too scant a context to feed educated guesses. But
> > this, at least, looks wrong to me:
> > 
> > > I also tried the following command:
> > > 
> > > emacs --geometry 2048x1024 --eval "(setq debug-on-error)" --debug-init &
> > ... it should be "(setq debug-on-error t)".
> 
> 
> A possible approach to backtracking on Linux might be to improve or enhance
> GNU emacs to use Ian Taylor's libbacktrace open source library. The
> libbacktrace source code is on
> https://github.com/ianlancetaylor/libbacktrace

[...]

Hi, Basile

I think (but I may be wrong, of course) the OP's problem was much simpler
and they were just after a plain boring Lisp stack trace.

That saie, I'm still a fan of your work :)

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-11-30 10:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAG9ihEvJq=iH-cVVHc3J2zNSXEnxg=8Tu02=P1nmgHz0cMpH8g@mail.gmail.com>
2023-11-29 21:43 ` Fwd: Fails to bring up a back trace Davin Pearson
2023-11-29 23:29   ` Emanuel Berg
2023-11-30  4:58   ` tomas
2023-11-30  9:47     ` Basile Starynkevitch
2023-11-30 10:17       ` tomas [this message]
2023-11-30 10:38         ` Basile Starynkevitch
2023-11-30 13:17   ` Michael Heerdegen via Users list for the GNU Emacs text editor

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

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

  git send-email \
    --in-reply-to=ZWhhHp9intNqGtSi@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=basile@starynkevitch.net \
    --cc=davin.pearson@gmail.com \
    --cc=gnu.emacs.help@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.