From: Troy Hinckley <t.macman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>
Cc: 60842@debbugs.gnu.org
Subject: bug#60842: 29.0.50; Crash when printing sqlite object
Date: Sun, 29 Jan 2023 00:36:40 -0700 [thread overview]
Message-ID: <2c09e4d8-1fa6-4838-b7e8-180818c0f7f8@Spark> (raw)
In-Reply-To: <28e8c678-6769-b4e3-93c4-54dc19475c11@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
Sorry for the long delay. I updated my Emacs version to the latest 29 commit and the issue went away. I am no longer able to reproduce it. Thank you for the quick reply and debug though!
On Jan 17, 2023 at 1:44 PM -0700, Paul Eggert <eggert@cs.ucla.edu>, wrote:
> On 1/16/23 05:16, Eli Zaretskii wrote:
>
> > char buf[max (sizeof "from..to..in " + 2 * INT_STRLEN_BOUND (EMACS_INT),
> > max (sizeof " . #" + INT_STRLEN_BOUND (intmax_t),
> > max ((sizeof " with data 0x"
> > + (sizeof (uintmax_t) * CHAR_BIT + 4 - 1) / 4),
> > 40)))];
> > current_thread->stack_top = buf; <<<<<<<<<<<<<<<<<<<<<<<<<<
> >
> > If you remove the indicated line, does the crash go away?
> >
> > If removing that line doesn't help, please tell the dimension of the
> > buf[] array that the code above calculates? In GDB, this is possible
> > with the command 'ptype'; I don't know what is the lldb equivalent.
>
> sizeof buf should be 54 on his platform, which I assume has 64-bit
> addresses and 64-bit u?intmax_t.
>
>
> > Paul, any ideas or suggestions?
>
> Unfortunately not.
>
[-- Attachment #2: Type: text/html, Size: 1687 bytes --]
next prev parent reply other threads:[~2023-01-29 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 23:38 bug#60842: 29.0.50; Crash when printing sqlite object Troy Hinckley
2023-01-16 13:16 ` Eli Zaretskii
2023-01-17 20:44 ` Paul Eggert
2023-01-29 7:36 ` Troy Hinckley [this message]
2023-01-29 7:55 ` Eli Zaretskii
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=2c09e4d8-1fa6-4838-b7e8-180818c0f7f8@Spark \
--to=t.macman@gmail.com \
--cc=60842@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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.