Issue72

classification
Title [Bug: 21.4.17] When calling perldb from a script, the current source line is not properly selected! (keywords: perl, debug, gud), Resolved
Type defect Module debug
Severity inconvenience Platform N/A
Keywords Nosy List
explanation
process
These controls should only be changed by committers and tracker administrators.
Status chatting   Reason
Superseder   Submitted 2007-11-09.21:39:55
Priority normal   Assigned To

Created on 2008-01-19.04:58:03 by stephen, last changed 2008-02-10.01:37:06 by T.Mittelstaedt.

Messages
msg550 [hidden] ([hidden]) Date: 2008-02-10.01:37:06
  Message-ID: <473840AE.7060105@cadenas.de>
Stephen,

The error usually sits in front of the computer, even though the perl 
documentation could be a bit more explicit about this:
I just had to modify my little script to contain -emacs like:

cat /tmp/stdin-17959.log | perl -d 
/buildcontrol/tinderbox/bin/processmail_builds_test.pl -emacs

A perldoc perl5db.pl tells you under 'SETTING UP THE TERMINAL' to 
specify -emacs as the first option after the script.

       If there is a TTY, we have to determine who it belongs to before 
we can
       proceed. If this is a slave editor or graphical debugger (denoted by
       the first command-line switch being '-emacs'), we shift this off and
       set $rl to 0 (XXX ostensibly to do straight reads).

Greetings,
thomas
msg476 [hidden] ([hidden]) Date: 2008-01-23.09:43:43
Supersedes issue160.
msg88 [hidden] ([hidden]) Date: 2008-01-19.04:58:03
  Message-ID: <87ejezm72s.fsf@uwakimon.sk.tsukuba.ac.jp>
Thomas Mittelstaedt writes:

 > In package debug, version 1.17, in function gud-perldb-marker-filter I
 > changed the following to get the desired behaviour!
 > 
 > ;     (while (string-match 
 > "^\032\032\\([a-zA-Z]:\\)?\\([^:\n]*\\):\\([0-9]*\\):.*\n"

Thanks for the report.  Do you have any idea why the \032 characters
(^Z) might have been put there in the first place?

 > 
 > ;; thmi changed the regex to the following. When I called the perl 
 > debugger from
 > ;; a script like
 > ;; cat /tmp/stdin-21164.log | perl -d 
 > /buildcontrol/tinderbox/bin/processmail_builds_test.pl
 > ;; the current source line would not show up in the other buffer
 > 
 >       (while (string-match 
 > "^\\([a-zA-Z]+\\)::[^:\n]*(\\([^:\n]*\\):\\([0-9]*\\)):"

This is quite different semantically from the regexp above, the
required double colon replaces a pair of colons separated by optional
text, and your regexp is not anchored at a newline at the end but the
one above is.  I think this is likely to have quite bad impacts on
other users.

Can you come up with more minimal changes that work for you?  (NB, I
don't use this feature so can't judge, thus I'm being conservative.
If you get better advice, please ignore me.)

_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta@xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
History
Date User Action Args
2008-02-10 01:37:06T.Mittelstaedtsetmessages: + msg550
title: [Bug: 21.4.17] When calling perldb from a script, the current source line is not properly selected! (keywords: perl, debug, gud) -> [Bug: 21.4.17] When calling perldb from a script, the current source line is not properly selected! (keywords: perl, debug, gud), Resolved
2008-01-23 09:43:43stephensetstatus: new -> chatting
severity: inconvenience
messages: + msg476
module: + debug
priority: normal
platform: + N/A
type: defect
2008-01-23 09:43:05stephenlinkissue160 superseder
2008-01-19 04:58:03stephencreate