unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: emacs-devel@gnu.org
Subject: Re: debugging.texi
Date: Thu, 16 Jun 2005 00:36:56 +0200	[thread overview]
Message-ID: <87hdfz5jsn.fsf@xs4all.nl> (raw)
In-Reply-To: <200506151850.j5FIo8Q24850@raven.dms.auburn.edu> (Luc Teirlinck's message of "Wed, 15 Jun 2005 13:50:08 -0500 (CDT)")

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> What about the following additional change to debugging.texi?  It may
> not be that surprising that if you can not step through a
> byte-compiled function, you can not step through a primitive function
> either, but it may not hurt to explicitly mention it.

I think your formulation is a bit misleading.  Emacs' debugger can't
step through a primitive, gdb can.

Lute.

  reply	other threads:[~2005-06-15 22:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 18:50 debugging.texi Luc Teirlinck
2005-06-15 22:36 ` Lute Kamstra [this message]
2005-06-15 23:31   ` debugging.texi Luc Teirlinck
2005-06-16  8:54     ` debugging.texi Lute Kamstra
  -- strict thread matches above, loose matches on Subject: below --
2005-06-09 22:36 debugging.texi Luc Teirlinck
2005-06-10 13:30 ` debugging.texi Richard Stallman
2005-06-11  3:30   ` debugging.texi Luc Teirlinck
2005-06-11  7:30     ` debugging.texi Lute Kamstra
2005-06-11 23:16       ` debugging.texi Richard Stallman
2005-06-11 23:16     ` debugging.texi Richard Stallman
2005-06-12  1:26       ` debugging.texi Luc Teirlinck
2005-06-12  8:19         ` debugging.texi Lute Kamstra
2005-06-11 12:18   ` debugging.texi Richard Stallman

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=87hdfz5jsn.fsf@xs4all.nl \
    --to=lute.kamstra.lists@xs4all.nl \
    --cc=emacs-devel@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 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).