From: Nick Roberts <nickrob@snap.net.nz>
To: Kenichi Handa <handa@ni.aist.go.jp>
Cc: wence@gmx.li, Dan Nicolaescu <dann@ics.uci.edu>,
emacs-pretest-bug@gnu.org
Subject: Re: --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient)
Date: Wed, 6 Feb 2008 15:36:57 +1300 [thread overview]
Message-ID: <18345.7497.113761.309963@kahikatea.snap.net.nz> (raw)
In-Reply-To: <E1JMYZn-0000qm-O5@etlken.m17n.org>
> > > Why not start the debugger in another terminal and attach to the emacs
> > > process?
> >
> > I tried it, but, when I type C-z on gdb terminal, gdb itself
> > is suspended.
>
> > Use C-c to get the gdb prompt, not C-z.
>
> When I type C-c in the gdb terminal, nothing happens except
> for beep sound.
Yes, I'm not sure if the signal handling in .gdbinit is appropriate for this
situation and signal handling appears to have changed in X. What happens if
you comment out the line
handle 2 noprint pass
in .gdbinit before starting gdb? Does typing C-c DTRT now?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-02-06 2:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 16:57 23.0.60; emacs segfaults when creating X display via emacsclient Lawrence Mitchell
2008-02-04 20:17 ` Lawrence Mitchell
2008-02-05 0:18 ` --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient) Dan Nicolaescu
2008-02-05 7:43 ` Kenichi Handa
2008-02-05 8:15 ` Dan Nicolaescu
2008-02-05 11:22 ` Kenichi Handa
2008-02-05 13:57 ` Dan Nicolaescu
2008-02-06 0:55 ` Kenichi Handa
2008-02-06 2:36 ` Nick Roberts [this message]
2008-02-06 15:28 ` Dan Nicolaescu
2008-02-13 12:42 ` Kenichi Handa
2008-02-13 13:38 ` --enable-font-backend bug Leo
2008-02-17 9:24 ` --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient) Kenichi Handa
2008-02-17 15:48 ` Dan Nicolaescu
2008-02-18 11:01 ` Kenichi Handa
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=18345.7497.113761.309963@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=dann@ics.uci.edu \
--cc=emacs-pretest-bug@gnu.org \
--cc=handa@ni.aist.go.jp \
--cc=wence@gmx.li \
/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.