unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: eric@mantis.styx.org
Subject: Emacs debugging help...
Date: 24 Oct 2002 14:01:55 -0400	[thread overview]
Message-ID: <vkznt34sx8.fsf@mantis.styx.org> (raw)

Hello All,

I've recently decided to begin developing and debugging emacs lisp
programs.  However, I'm not sure how to use the debugger, and, for
anything more complicated than a simple function, the documentation
I've discovered is less than adequate.

The particulars of the current situation are:

I'm using VM for reading mail.  When my sister sends me email from
work, she uses Microsoft Outlook, which writes HTML mail.  Now, I know
this is wrong, and I've tried to convince her otherwise, but at this
point the politics are less interesting to me than the technology.  In
any case, VM tries to display the HTML email with w3, and w3 fails
(somewhere).  However, VM is written well, and catches the error, and
does something else.  I want to figure out what went wrong, that I
might fix it.

VM reports the failure to *Messages* as

Inline HTML display failed: (wrong-type-argument stringp nil)

which is generated in a particular function in a 

(condition-case 
   ...)

Now, when I set 'debug-on-error' to t, Emacs doesn't drop into the
debugger at the time this error is raised.  I guess that's because it
doesn't pick this up as an error, (because the error never makes it to
the toplevel?) and I have no debugging information; just the (sort of)
bad behaviour.

Now, if I put a 

(debug) 

just before the function call in the VM source code, recompile and
reinstall, I get into the (not too well understood by me yet) debugger
at around the right time, but then there's still reams of code to step
through (manually, with the 'd' key).

Clearly, there has to be a better way.  What am I missing?

What I'm looking for are useful tips, tricks, and general debugging
advice, that I might be a more productive and useful member of the
community.

I have the latest VM and w3 sources, and would like to understand
these projects better.  I figure that fixing things which bother me is
a good way to start.

Thanks,

Eric
** 
Eric Moncrieff                                    eric@mantis.styx.org

"If, in your bold creative way, you hold yourself free to draw a 
giraffe with a short neck, you will really find that you are not 
free to draw a giraffe."  --G. K. Chesterton
**
GPG Fingerprint: C278 AECC 3292 C26B E9DA  0FD7 EE20 4AA7 E1AD 0D79

             reply	other threads:[~2002-10-24 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 18:01 eric [this message]
2002-10-24 20:19 ` Emacs debugging help D. Goel
2002-11-02 17:47 ` Ivan Kanis
  -- strict thread matches above, loose matches on Subject: below --
2002-11-04 15:32 Bingham, Jay

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=vkznt34sx8.fsf@mantis.styx.org \
    --to=eric@mantis.styx.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.
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).