From: Andrea Corallo 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, 09 Feb 2021 20:43:43 +0000 [thread overview]
Message-ID: <xjfh7mlx98g.fsf@sdf.org> (raw)
In-Reply-To: <CAPDfab4dsrXpMjJaszX1dHedEkOq9rm4TAuKQQFxKvBucGp3Tg@mail.gmail.com> (Justin Schell's message of "Mon, 8 Feb 2021 12:49:01 -0800")
Justin Schell <justinmschell@gmail.com> writes:
>> 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
>
> Hi Andrea,
>
> So, I was able to build emacs with debug symbols and run via gdb as
> directed above, but unfortunately, gdb doesn't hit the breakpoint when
> I run `M-x report-emacs-bug`. gdb does break quite a few times (770
> times, to be exact) on `wrong_type_argument` during startup, though. I
> looked at the emacs source a bit to try to put a breakpoint somewhere
> that would be more fruitful, but I didn't really see where I would do
> so.
I think we are likely to be interested only in the last occurence. You
can ignore the breakpoint 769 times to see what's going on:
(gdb) b wrong_type_argument
Breakpoint 5 at 0x58a0a2: file data.c, line 143.
(gdb) ignore 5 769
Will ignore next 769 crossings of breakpoint 5.
(gdb) run
Thanks
Andrea
next prev parent reply other threads:[~2021-02-09 20:43 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjfh7mlx98g.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).