GNU bug report logs - #45701
28.0.50; [feature/native-comp] (33b8ce8) `M-x report-emacs-bug` error: "Wrong type argument: stringp, nil"

Previous Next

Package: emacs;

Reported by: Justin Schell <justinmschell <at> gmail.com>

Date: Wed, 6 Jan 2021 19:26:01 UTC

Severity: normal

Found in version 28.0.50

Done: Andrea Corallo <akrl <at> sdf.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Andrea Corallo <akrl <at> sdf.org>
To: Justin Schell <justinmschell <at> gmail.com>
Cc: 45701 <at> debbugs.gnu.org, contact <at> jimeh.me
Subject: bug#45701: 28.0.50; [feature/native-comp] (33b8ce8) `M-x report-emacs-bug` error: "Wrong type argument: stringp, nil"
Date: Wed, 03 Feb 2021 20:31:21 +0000
Justin Schell <justinmschell <at> gmail.com> writes:

>> BTW dumb question: the issue is present also running "emacs -Q" right?
>
> Yes.
>
>> one could also place the breackpoint from gdb for an interactive
>> session, is just a little more annoying if one want to re-run multiple
>> times while debugging.
>
> Trying to do that, but I have no idea what I'm doing with gdb. The
> following doesn't seem to do anything useful. It does seem to run an
> emacs process, but there's no window that comes up for me to interact
> with and nothing else seems to happen:

I think the idea would be ~ to:

- compile with debug symbols

- start gdb loading emacs

- source .gdbinit

- add a breakpoint in 'wrong_type_argument'

- run Emacs and let the error happen

- At this point gdb should take control and you should be able to type
  'bt' to obtain and report the backtrace

Thanks

  Andrea




This bug report was last modified 4 years and 105 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.