Fwd: Fails to bring up a back trace

Fwd: Fails to bring up a back trace

[Davin Pearson]

--
Sincerely and kindest regards,
*Davin Pearson* http://davin.50webs.com




---------- Forwarded message ---------
From: Davin Pearson <davin.pearson@gmail.com>
Date: Thu, 30 Nov 2023 at 10:37
Subject: Fails to bring up a back trace
To: <gnu.emacs.help@googlegroups.com>


When I run my code, it spews out the following error message:

Symbol's function definition is void: t

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the ‘--debug-init’ option to view a complete error backtrace.

Here is the contents of my runmacs.bat file:

emacs --geometry 2048x1024 --debug-init &

Yet it fails to bring up an error backtrace.

I also tried the following command:

emacs --geometry 2048x1024 --eval "(setq debug-on-error)" --debug-init &

What gives?

--
Sincerely and kindest regards,
*Davin Pearson* http://davin.50webs.com

Re: Fwd: Fails to bring up a back trace

[Emanuel Berg]

Davin Pearson wrote:

> Symbol's function definition is void: t
>
> To ensure normal operation, you should investigate and remove the
> cause of the error in your initialization file.  Start Emacs with
> the ‘--debug-init’ option to view a complete error backtrace.
>
> Here is the contents of my runmacs.bat file:
>
> emacs --geometry 2048x1024 --debug-init &
>
> Yet it fails to bring up an error backtrace.
>
> I also tried the following command:
>
> emacs --geometry 2048x1024 --eval "(setq debug-on-error)" --debug-init &
>
> What gives?

Should be (setq debug-on-error t)

Maybe that is what you have in code as well?

Peace.

-- 
underground experts united
https://dataswamp.org/~incal

Re: Fwd: Fails to bring up a back trace

[tomas]

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

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)".

Cheers
-- 
t

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

Re: Fwd: Fails to bring up a back trace

[Basile Starynkevitch]

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

On Linux, mixing that library with the dladdr function (see 
https://man7.org/linux/man-pages/man3/dladdr.3.html) gives human 
readable backtraces.

And this is used both in recent GCC compilers (see https://gcc.gnu.org/ 
- the source code of libbacktrace is incorporated in GCC 13...) and in 
the RefPerSys open source inference engine project on 
https://github.com/RefPerSys/RefPerSys/

It seems that the latest GNU emacs snapshot commit e87644baa3239ce5 is 
using GNU libc backtracing functions, but not (like GCC does) the 
libbacktrace from Ian Taylor.

For details, contact me (Basile Starynkevitch, in France near Paris) by 
email to basile@starynkevitch.net

Regards

-- 
Basile Starynkevitch
  <basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/

Re: Fwd: Fails to bring up a back trace

[tomas]

[-- 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 --]

Re: Fwd: Fails to bring up a back trace

[Basile Starynkevitch]

On 11/30/23 11:17, tomas@tuxteam.de wrote:
> 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.


But recent GNU emacs can be built to use the libgccjit library to 
translate emacs lisp code to machine code, and can also be built to 
accept emacs modules, that is dlopen-ed shared libraries. See 
https://phst.eu/emacs-modules.html

I tend to believe that a plain boring Lisp stack trace is not always 
enough (since emacs lisp bytecode is sometimes translated to maching 
code, or because of emacs modules).


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


Thanks. The issue is find funding and ITEA or HorizonEurope consortium 
supporting https://github.com/RefPerSys/RefPerSys/

>
> Cheers

-- 
Basile Starynkevitch
  <basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/

Re: Fwd: Fails to bring up a back trace

[Michael Heerdegen via Users list for the GNU Emacs text editor]

Davin Pearson <davin.pearson@gmail.com> writes:

> When I run my code, it spews out the following error message:

What does "I run my code" mean?

Michael.