From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Debugging Perl with Emacs / perldb
Date: Mon, 2 Aug 2010 21:42:25 +0000 (UTC) [thread overview]
Message-ID: <slrni5eeu1.gtf.nospam-abuse@powdermilk.math.berkeley.edu> (raw)
In-Reply-To: mailman.4.1280755881.17287.help-gnu-emacs@gnu.org
On 2010-08-01, William L Brown <bbrown@addtoit.com> wrote:
> Nothing but an indicator of what line I am running with no view of the
> line:
> (eval 6)[/home/bbrown/newTmp/emacsDebugTests/foo.pl:8]:7:0
From this info, an external program cannot deduce what happens. We
know that we are on 7th line of $foo, and that
eval $foo
was called on the 8th line of
/home/bbrown/newTmp/emacsDebugTests/foo.pl. But how would Emacs know
what is the contents of $foo?
Perl's debugger is not READING scripts to find "the code on line 6 of
bar.pl"; Perl (in debugging mode) just keeps the array of lines SEEN
by the compiler (an array per each file). For Perl, this $foo becomes
just another "input file", so it has the associated array, and Perl's
debugger can inspect what is on 7th line of this $foo.
Emacs' debugging, on the other hand, is based on reading "raw files"
from the filesystem. I see no easy way to communicate the needed info by
IPC... [*]
Hope this helps,
Ilya
P.S. [*] Of course, one can extract the relevant arrays from Perl
(using, e.g., the `l' operator). But this would require some
extra parsing...
next parent reply other threads:[~2010-08-02 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4.1280755881.17287.help-gnu-emacs@gnu.org>
2010-08-02 21:42 ` Ilya Zakharevich [this message]
2010-08-01 13:34 Debugging Perl with Emacs / perldb William L Brown
2010-08-02 14:31 ` Gary
[not found] ` <mailman.8.1280759507.17287.help-gnu-emacs@gnu.org>
2010-08-03 18:45 ` Joseph Brenner
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=slrni5eeu1.gtf.nospam-abuse@powdermilk.math.berkeley.edu \
--to=nospam-abuse@ilyaz.org \
--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.
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.