Has anyone tried debugging fork process usings emacs perldb debugger? I tried using the above xterm method discussed in the article, I was able to successfully create an xterm for each child process but I can't view the source code from the child window with debugger commands, such as 'l'ine command. I can issue 'n'ext and 's'tep from the child and see its output in the parent window. But its not helpful if I can't easily tell where i am in the source code for the child. Any idea what is wrong?
What I would really like is to be able to fork another emacs debugger process with debugger command and source code window for each child similar to the parent.
Any help would be greatly appreciated
Kelly
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|