all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: 23.0.60; Still font problems
Date: Fri, 16 May 2008 09:41:42 +0900	[thread overview]
Message-ID: <E1Jwo10-0002uO-9C@etlken.m17n.org> (raw)
In-Reply-To: <87zlqrbsej.fsf@escher.local.home> (message from Stephen Berman on Thu, 15 May 2008 15:36:52 +0200)

In article <87zlqrbsej.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:

> I have now managed to step through till the point of failure.  Since I
> determined by trial and error that it was over 27000 steps after the
> break point, I used `s 27000' and then single stepped.  Here's the
> output of the latter; if it's not useful, I don't know what else to do
> -- I can't take the time to single step through 27000 lines of code.

The command to step one line by one is `n(ext)'.  The
command `s(tep)' should be used only when you want to step
into a function called at the current line.  The `fin(ish)'
command is also useful to execute until the current function
returns.  You can also check the type/value of a
Lisp_Object.  See etc/DEBUG for the detail.

---
Kenichi Handa
handa@ni.aist.go.jp




  reply	other threads:[~2008-05-16  0:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 16:52 23.0.60; Still font problems jpff
2008-05-15  0:43 ` Kenichi Handa
2008-05-15  7:05   ` jpff
2008-05-15  7:38     ` Kenichi Handa
2008-05-15  8:32       ` Stephen Berman
2008-05-15  8:40         ` Jason Rumney
2008-05-15 10:03           ` Stephen Berman
2008-05-15 13:36             ` Stephen Berman
2008-05-16  0:41               ` Kenichi Handa [this message]
2008-05-16 14:44                 ` Stephen Berman

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=E1Jwo10-0002uO-9C@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=Stephen.Berman@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@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.