unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "YUSUF ALPER ÇIKIŞIR" <yusufcikisir@std.iyte.edu.tr>
Cc: 59715@debbugs.gnu.org
Subject: bug#59715: 28.2; Emacs crashes after ``turkish-case-conversion-enable''
Date: Sun, 04 Dec 2022 19:38:31 +0200	[thread overview]
Message-ID: <83ilir9ii0.fsf@gnu.org> (raw)
In-Reply-To: <878rjn1dd4.fsf@std.iyte.edu.tr> (yusufcikisir@std.iyte.edu.tr)

> From: YUSUF ALPER ÇIKIŞIR
>  <yusufcikisir@std.iyte.edu.tr>
> Cc: 59715@debbugs.gnu.org
> Date: Sun, 04 Dec 2022 16:56:39 +0300
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Then, when the breakpoint breaks, look at the name it displays and see if
> > you see some pattern that has "Iosevka" in it.  You will have to type
> > "continue" each time the breakpoint breaks, to continue Emacs.  If I'm
> > right, you will see something with "Iosevka" in it.
> 
> I'm not seeing the "Iosevka" string.

Well, another, perhaps crude way is like this: add to the function Fdowncase
some simple code which will detect when it is called with the string that
matches "Iosevka", and will call some function, like emacs_abort.  Then you
can put a breakpoint at the line of this call, and when it breaks, see what
the C-level backtrace tells us.

Would you like to try that?  If so, I can help you write that code snippet.

Thanks.





  reply	other threads:[~2022-12-04 17:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30  3:10 bug#59715: 28.2; Emacs crashes after ``turkish-case-conversion-enable'' YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-30 16:12 ` Eli Zaretskii
2022-12-01  2:11   ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01  7:26     ` Eli Zaretskii
2022-12-01 22:26       ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-02  7:23         ` Eli Zaretskii
2022-12-03 22:09         ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04  7:16           ` Eli Zaretskii
2022-12-04  8:29             ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04  8:33             ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 10:20               ` Eli Zaretskii
2022-12-04 11:44                 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 12:09                   ` Eli Zaretskii
2022-12-04 12:17                     ` Eli Zaretskii
2022-12-04 12:46                     ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 12:56                       ` Eli Zaretskii
2022-12-04 13:10                         ` Eli Zaretskii
2022-12-04 13:21                         ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 13:39                           ` Eli Zaretskii
2022-12-04 13:56                             ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 17:38                               ` Eli Zaretskii [this message]
2022-12-05  2:29                                 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 13:23                                   ` Eli Zaretskii
2022-12-06 16:09                                     ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-06 16:20                                       ` Eli Zaretskii
2022-12-01  2:23   ` YUSUF ALPER ÇIKIŞIR 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=83ilir9ii0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59715@debbugs.gnu.org \
    --cc=yusufcikisir@std.iyte.edu.tr \
    /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).