unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59715@debbugs.gnu.org
Subject: bug#59715: 28.2; Emacs crashes after ``turkish-case-conversion-enable''
Date: Sun, 04 Dec 2022 16:56:39 +0300	[thread overview]
Message-ID: <878rjn1dd4.fsf@std.iyte.edu.tr> (raw)
In-Reply-To: <83v8mr9tl1.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Dec 2022 15:39:06 +0200")

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.

(gdb) source ~/repo/emacs-28.2/src/.gdbinit
SIGINT is used by the debugger.
Are you sure you want to change it? (y or n) [answered Y; input not from terminal]
DISPLAY = :0.0
TERM = screen.xterm-256color
Breakpoint 1 at 0x562dda: file emacs.c, line 400.
Breakpoint 2 at 0x53af51: file xterm.c, line 10291.
(gdb) break fontset.c:1701
Breakpoint 3 at 0x6c297a: file fontset.c, line 1701.
(gdb) commands
Type commands for breakpoint(s) 3, one per line.
End with a line saying just "end".
>pp name
>end
(gdb) run -Q
Starting program: /home/ytc/repo/emacs-28.2/src/emacs -Q
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
[New LWP 4536]

Thread 1 "emacs" hit Breakpoint 3, Fnew_fontset (name=XIL(0x7ffff5399ecc), fontlist=XIL(0xc94393)) at fontset.c:1701
1701      name = Fdowncase (name);
"fontset-default"
(gdb) continue
Continuing.

Thread 1 "emacs" hit Breakpoint 3, Fnew_fontset (name=XIL(0xe4bdc4), fontlist=XIL(0)) at fontset.c:1701
1701      name = Fdowncase (name);
"-*-fixed-medium-r-normal-*-16-*-*-*-*-*-fontset-standard"
(gdb) continue
Continuing.

Thread 1 "emacs" hit Breakpoint 1, terminate_due_to_signal (sig=6, backtrace_limit=40) at emacs.c:400
400       signal (sig, SIG_DFL);

> Yes.  One other idea is to use Fontconfig aliases, so that the font can be
> named differently as far as Emacs is concerned, but I'm not sure it will
> help.

I will look into that.





  reply	other threads:[~2022-12-04 13:56 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 [this message]
2022-12-04 17:38                               ` Eli Zaretskii
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=878rjn1dd4.fsf@std.iyte.edu.tr \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59715@debbugs.gnu.org \
    --cc=eliz@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).