From: akrl--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Justin Schell <justinmschell@gmail.com>
Cc: 45701@debbugs.gnu.org, contact@jimeh.me
Subject: bug#45701: 28.0.50; [feature/native-comp] (33b8ce8) `M-x report-emacs-bug` error: "Wrong type argument: stringp, nil"
Date: Tue, 02 Feb 2021 09:05:39 +0000 [thread overview]
Message-ID: <xjfr1lysuu4.fsf@sdf.org> (raw)
In-Reply-To: <CAPDfab7mN2YhU8PHr4BNHVf9rLBbC+Ni0HtTBvxhaduJ4NXWGg@mail.gmail.com> (Justin Schell's message of "Mon, 1 Feb 2021 15:10:58 -0800")
Justin Schell <justinmschell@gmail.com> writes:
>> emacs -batch -eval '(report-emacs-bug "")'
>
> Ah, sorry, I misunderstood as I had never heard of batch mode before.
>
> Simply calling `report-emacs-bug` did not do the trick:
> ```
> [builds (master-)]$
> Emacs.app-\[feature-native-comp\]\[2021-01-30\]\[a8b8d22\]\[macOS-10.15\]\[x86_64\].app/Contents/MacOS/Emacs
> -batch -eval '(progn (message "foo") (report-emacs-bug "") (message
> "bar"))'
> foo
> Checking for load-path shadows...
> Checking for load-path shadows...done
> bar
> [builds (master-)]$
> ```
>
> I'll continue to try to figure out how to repro, though.
>
> Justin
Hi Justin,
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.
BTW dumb question: the issue is present also running "emacs -Q" right?
Thanks
Andrea
next prev parent reply other threads:[~2021-02-02 9:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 19:16 bug#45701: 28.0.50; [feature/native-comp] (33b8ce8) `M-x report-emacs-bug` error: "Wrong type argument: stringp, nil" Justin Schell
2021-01-06 19:28 ` Eli Zaretskii
2021-01-06 20:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-06 20:46 ` Justin Schell
2021-01-06 20:48 ` Jim Myhrberg
2021-01-06 23:54 ` Jim Myhrberg
2021-01-07 0:45 ` Justin Schell
2021-01-07 22:45 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-08 0:20 ` Justin Schell
2021-01-08 11:18 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-08 14:47 ` Justin Schell
2021-01-08 15:37 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-01 21:13 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-01 21:51 ` Justin Schell
2021-02-01 22:21 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-01 23:10 ` Justin Schell
2021-02-02 9:05 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-02-03 1:30 ` Justin Schell
2021-02-03 20:31 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-03 20:36 ` Justin Schell
2021-02-08 20:49 ` Justin Schell
2021-02-08 20:57 ` Justin Schell
2021-02-09 20:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-09 21:10 ` Justin Schell
2021-02-09 21:23 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-09 21:33 ` Justin Schell
2021-02-10 3:18 ` Jim Myhrberg
2021-02-10 4:40 ` Justin Schell
2021-02-10 9:09 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=xjfr1lysuu4.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=45701@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=contact@jimeh.me \
--cc=justinmschell@gmail.com \
/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.