Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#2 debugger output was not parsed correctly

closed-out-of-date
nobody
None
5
2006-10-07
2005-10-21
MINAMI Hirokazu
No

In PerlDB::getCurrent_IP_Position(),
currnt instruction pointer's position seems to be
extracted from
a perl5db's output which looks like:
dumpvar_epic::dumpvar_epic(c:/eclipse/plugins/org.epic.debug_0.3.2//dumpvar_epic.pm:449):
449: my ($package,$m,@vars) =
@_;-------------------------------

However, the output sometimes can take another form:
Win32::API::Type::CODE(0x1e4f9c4)(C:/Perl/site/lib/Win32/API/Type.pm:40):
40: my $section = 'nothing';

in this case, the filename to be debugged is considered as:
0x1e4f9c4)(C:/Perl/site/lib/Win32/API/Type.pm
but such a file does not exists in most case.

attached is a patch to sanitize filenaes by assumig
that filenames would not contain ")(".

Discussion

  • Logged In: YES
    user_id=203671

    Sorry. I fogot to attach the patch.

     
  • patch to remove leading garbages from file names

     
  • Jan Ploski
    Jan Ploski
    2006-10-07

    • status: open --> closed-out-of-date
     
  • Jan Ploski
    Jan Ploski
    2006-10-07

    Logged In: YES
    user_id=86907

    Unfortunately, I overlooked this patch and fixed the
    problem myself in 0.5.7. Thanks anyway.