unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: (debug) backtrace: how to show source code at current location.
Date: Thu, 06 Jan 2011 10:31:36 +1100	[thread overview]
Message-ID: <871v4rapwn.fsf@puma.rapttech.com.au> (raw)
In-Reply-To: mailman.0.1294256637.13904.help-gnu-emacs@gnu.org

Larry Evans <cppljevans@suddenlink.net> writes:

> On 01/05/11 13:06, Drew Adams wrote:
>>> Please, how can I find out what's causing this error message:
>>>
>>>   "(wrong-type-argument arrayp tab)"
>> 
>> From your error message alone, it seems that the symbol `tab' is being passed to
>> some function that expects an array.  That's not much help yet, but things might
>> become clearer when you dig deeper using the debugger.
>> 
>> (setq debug-on-error t)
>> 
>> 1. Load source (*.el) files for the library where the error occurred.
>> 
>> IOW, look at the `debug-on-error' backtrace to see which function(s) were
>> involved when the error occurred.  Then use `C-h f' or `find-func' to find the
>> function definition(s) (source file(s)).  Load the source file(s) (*.el) using
>> `load-file' or `load-library', including the extension `.el' in the name.
>> 
>> 2. Provoke the error and backtrace again.  It should now show more source-code
>> entry points instead of byte-code (the `(byte-code "ÁÂÃ...' stuff)
>> 
>> 3. You can also use `M-x debug-on-entry THE-FUNCTION' to enter the debugger
>> whenever a problematic function is invoked.  Then you can walk through the
>> invocation to see more about what caused the error.
>> 
>> 
>> 
> Thank you very much for the help Drew.
> What I did was started with just:
>
>   (setq debug-on-error t)
>
> as shown in the attachment (a revision of the one posted earlier).
> The started emacs; however, no backtrace appeared.  OTOH, the
> *Messages* buffer contained:
>
>> Loading /home/evansl/.emacs.d/init.common.el (source)...
>> Loading /home/evansl/.recentf...done
>> Cleaning up the recentf list...done (0 removed)
>> Loading /usr/share/emacs/site-lisp/haskell-mode/haskell-site-file.el (source)...done
>> Loading /home/evansl/.emacs.d/init.common.el (source)...done
>> Loading desktop...done
>> Loading eldoc...done
>> uncompressing indent.el.gz...done
>> Note: file is write protected
>> Loading cc-mode...done
>> Note: file is write protected
>> c-tab-stop-my-list message
>> c++-mode-my-hook message:tabs=
>> (0 2 4)
>> c++-mode-my-hook message{
>> File mode specification error: (wrong-type-argument arrayp tab)
>> Loading /usr/share/emacs/site-lisp/haskell-mode/haskell-mode.el (source)...done
>
> Is there something else I should do to get a backtrace?
>

Yep, start emacs as 

emacs --debug-init

Tim

-- 
tcross (at) rapttech dot com dot au


  parent reply	other threads:[~2011-01-05 23:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 18:07 (debug) backtrace: how to show source code at current location Larry Evans
2011-01-05 19:06 ` Drew Adams
2011-01-05 19:43   ` Larry Evans
2011-01-05 19:54     ` Larry Evans
2011-01-05 19:58     ` Drew Adams
     [not found]   ` <mailman.0.1294256637.13904.help-gnu-emacs@gnu.org>
2011-01-05 23:31     ` Tim X [this message]
2011-01-06  2:53       ` Larry Evans
2011-01-06  3:50         ` Larry Evans
2011-01-06  3:55         ` Drew Adams
2011-01-06  4:50           ` Larry Evans
2011-01-06 13:57             ` Drew Adams

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=871v4rapwn.fsf@puma.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --cc=help-gnu-emacs@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.
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).