[perl #56558] [PATCH] pdb rename to parrot_pdb
Added NEWS entry in r29587. Closing ticket.
Re: [perl #56558] [PATCH] pdb rename to parrot_pdb
On Thu, Jul 17, 2008 at 9:46 AM, François Perrad <[EMAIL PROTECTED]> wrote: > pdb was renamed parrot_debugger, but not installable_pdb. Done in r29556, thanks. -- Salu2
Re: [perl #56558] [PATCH] pdb rename to parrot_pdb
NotFound a écrit : After some discussion in #parrotsketch, the name parrot_debugger wins. Done in r29496, waiting for comments and fixes before closing the ticket. pdb was renamed parrot_debugger, but not installable_pdb. François.
Re: [perl #56558] [PATCH] pdb rename to parrot_pdb
Fixed parrot_debugger test in r29508 -- Salu2
Re: [perl #56558] [PATCH] pdb rename to parrot_pdb
> After some discussion in #parrotsketch, the name parrot_debugger wins. Done in r29496, waiting for comments and fixes before closing the ticket. -- Salu2
Re: [perl #56558] [PATCH] pdb rename to parrot_pdb
>> I don't like the name parrot_pdb. 'parrot Parrot DeBugger' ? Looks >> redundant. After some discussion in #parrotsketch, the name parrot_debugger wins. -- Salu2
Re: [perl #56558] [PATCH] pdb rename to parrot_pdb
NotFound schrieb: On Tue, Jul 15, 2008 at 3:58 PM, Reini Urban via RT <[EMAIL PROTECTED]> wrote: This got warnocked for 0.6.4 rename the debugger, not the disassembler. I don't like the name parrot_pdb. 'parrot Parrot DeBugger' ? Looks redundant. I'll vote for parrot_debug Note that I listed at http://rt.perl.org/rt3/Public/Bug/Display.html?id=56558 the existing conflicts: pdb, the python debugger and the IBM parallel debugger. -- Reini Urban http://phpwiki.org/ http://murbreak.at/
Re: [perl #56558] [PATCH] pdb rename to parrot_pdb
On Tue, Jul 15, 2008 at 3:58 PM, Reini Urban via RT <[EMAIL PROTECTED]> wrote: > This got warnocked for 0.6.4 > > rename the debugger, not the disassembler. I don't like the name parrot_pdb. 'parrot Parrot DeBugger' ? Looks redundant. I'll vote for parrot_debug -- Salu2
[perl #56558] [PATCH] pdb rename to parrot_pdb
This got warnocked for 0.6.4 rename the debugger, not the disassembler. -- Reini Urban
[perl #56558] [PATCH] pdb rename to parrot_pdb
Added patch -- Reini Urban 2008-07-03 17:17:39 rurban * requires a svn rename before: svn rename src/pdb.c src/parrot_pdb.c svn rename t/tools/pdb.t t/tools/parrot_pdb.t * MANIFEST, docs/debug.pod, docs/debugger.pod, docs/parrot.pod src/parrot_pdb.c, t/tools/parrot_pdb.t: rename pdb to parrot_pdb to avoid conflicts with existing pdb binaries - e.g. the python debugger or the IBM parallel debugger. Index: parrot-svn/MANIFEST === --- parrot-svn.orig/MANIFEST +++ parrot-svn/MANIFEST @@ -3070,7 +3070,7 @@ src/packfile/pf_items.c src/packout.c [] src/pbc_info.c [] src/pbc_merge.c [] -src/pdb.c [] +src/parrot_pdb.c[] src/pdump.c [] src/pic.c [] src/pic_jit.c [] @@ -3857,7 +3857,7 @@ t/tools/ops2pmutils/09-prepare_real_ops. t/tools/ops2pmutils/10-print_module.t [] t/tools/ops2pmutils/11-print_h.t[] t/tools/pbc_merge.t [] -t/tools/pdb.t [] +t/tools/parrot_pdb.t[] t/tools/pmc2c.t [] t/tools/pmc2cutils/00-qualify.t [] t/tools/pmc2cutils/01-pmc2cutils.t [] Index: parrot-svn/docs/debug.pod === --- parrot-svn.orig/docs/debug.pod +++ parrot-svn/docs/debug.pod @@ -75,9 +75,9 @@ different objects over the lifetime of t Let's say you have written (or generated) a huge .pasm or .pir file. It's not working. You'd like some help in figuring out why. -=head2 pdb +=head2 parrot_pdb -One possible tool is C, the Parrot Debugger. See F for +One possible tool is C, the Parrot Debugger. See F for details on it. =head2 stabs Index: parrot-svn/docs/debugger.pod === --- parrot-svn.orig/docs/debugger.pod +++ parrot-svn/docs/debugger.pod @@ -7,12 +7,12 @@ docs/debugger.pod - The Parrot Debugger =head1 ABSTRACT -This document describes F, the Parrot Debugger. +This document describes F, the Parrot Debugger. =head1 DESCRIPTION Starting from version 0.0.6 Parrot has its own debugger, which is modeled after -Perl's one. Its name is F, and is an interactive environment that let you +Perl's one. Its name is F, and is an interactive environment that let you step through bytecode, set breakpoints, evaluate assembly instructions and peek at the interpreter status. @@ -29,17 +29,17 @@ target: (where C is the same C incarnation you used to build Parrot). -If everything goes well, you should come up with a F executable in the +If everything goes well, you should come up with a F executable in the same directory as the Parrot program. =head1 THE DEBUGGER SHELL To start the debugger type: - pdb file.pbc + parrot_pdb file.pbc -That is, F takes exactly one argument, which is the Parrot bytecode that -you're going to debug. F will automatically load and disassemble the +That is, F takes exactly one argument, which is the Parrot bytecode that +you're going to debug. F will automatically load and disassemble the bytecode file for you. Note that you can't pass command line arguments to your program when you invoke @@ -49,7 +49,7 @@ After the version banner, you'll see the (pdb) -F is ready to receive commands and give output. To list the available +F is ready to receive commands and give output. To list the available commands type 'h'. To quit the debugger type 'q'. As with the Perl debugger, whenever it halts and shows you a line of code, it @@ -69,7 +69,7 @@ sensitive. A blank line always repeats the last command entered. -Also note that at this point in its development, F has very poor error +Also note that at this point in its development, F has very poor error checking on commands and their arguments, so type carefully or something bad will happen. Feel free to report bugs, or better yet patch the source code (see L below). Index: parrot-svn/docs/parrot.pod === --- parrot-svn.orig/docs/parrot.pod +++ parrot-svn/docs/parrot.pod @@ -112,7 +112,7 @@ A beginner's guide to debugging the Parr =item F -Documentation for C, the Parrot debugger. +Documentation for C, the Parrot debugger. =back Index: parrot-svn/src/parrot_pdb.c === --- parrot-svn.orig/src/parrot_pdb.c +++ parrot-svn/src/parrot_pdb.c
[perl #56558] [PATCH] pdb rename to parrot_pdb
# New Ticket Created by Reini Urban # Please include the string: [perl #56558] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=56558 > --- osname= cygwin osvers= 1.5.25(0.15642) arch= cygwin-thread-multi-64int cc= gcc --- Flags: category=core severity=medium ack=no --- 2008-07-03 17:17:39 rurban * requires a svn rename before: svn rename src/pdb.c src/parrot_pdb.c svn rename t/tools/pdb.t t/tools/parrot_pdb.t * MANIFEST, docs/debug.pod, docs/debugger.pod, docs/parrot.pod src/parrot_pdb.c, t/tools/parrot_pdb.t: rename pdb to parrot_pdb to avoid conflicts with existing pdb binaries - e.g. the python debugger or the IBM parallel debugger. Index: parrot-svn/MANIFEST === --- parrot-svn.orig/MANIFEST +++ parrot-svn/MANIFEST @@ -3070,7 +3070,7 @@ src/packfile/pf_items.c src/packout.c [] src/pbc_info.c [] src/pbc_merge.c [] -src/pdb.c [] +src/parrot_pdb.c[] src/pdump.c [] src/pic.c [] src/pic_jit.c [] @@ -3857,7 +3857,7 @@ t/tools/ops2pmutils/09-prepare_real_ops. t/tools/ops2pmutils/10-print_module.t [] t/tools/ops2pmutils/11-print_h.t[] t/tools/pbc_merge.t [] -t/tools/pdb.t [] +t/tools/parrot_pdb.t[] t/tools/pmc2c.t [] t/tools/pmc2cutils/00-qualify.t [] t/tools/pmc2cutils/01-pmc2cutils.t [] Index: parrot-svn/docs/debug.pod === --- parrot-svn.orig/docs/debug.pod +++ parrot-svn/docs/debug.pod @@ -75,9 +75,9 @@ different objects over the lifetime of t Let's say you have written (or generated) a huge .pasm or .pir file. It's not working. You'd like some help in figuring out why. -=head2 pdb +=head2 parrot_pdb -One possible tool is C, the Parrot Debugger. See F for +One possible tool is C, the Parrot Debugger. See F for details on it. =head2 stabs Index: parrot-svn/docs/debugger.pod === --- parrot-svn.orig/docs/debugger.pod +++ parrot-svn/docs/debugger.pod @@ -7,12 +7,12 @@ docs/debugger.pod - The Parrot Debugger =head1 ABSTRACT -This document describes F, the Parrot Debugger. +This document describes F, the Parrot Debugger. =head1 DESCRIPTION Starting from version 0.0.6 Parrot has its own debugger, which is modeled after -Perl's one. Its name is F, and is an interactive environment that let you +Perl's one. Its name is F, and is an interactive environment that let you step through bytecode, set breakpoints, evaluate assembly instructions and peek at the interpreter status. @@ -29,17 +29,17 @@ target: (where C is the same C incarnation you used to build Parrot). -If everything goes well, you should come up with a F executable in the +If everything goes well, you should come up with a F executable in the same directory as the Parrot program. =head1 THE DEBUGGER SHELL To start the debugger type: - pdb file.pbc + parrot_pdb file.pbc -That is, F takes exactly one argument, which is the Parrot bytecode that -you're going to debug. F will automatically load and disassemble the +That is, F takes exactly one argument, which is the Parrot bytecode that +you're going to debug. F will automatically load and disassemble the bytecode file for you. Note that you can't pass command line arguments to your program when you invoke @@ -49,7 +49,7 @@ After the version banner, you'll see the (pdb) -F is ready to receive commands and give output. To list the available +F is ready to receive commands and give output. To list the available commands type 'h'. To quit the debugger type 'q'. As with the Perl debugger, whenever it halts and shows you a line of code, it @@ -69,7 +69,7 @@ sensitive. A blank line always repeats the last command entered. -Also note that at this point in its development, F has very poor error +Also note that at this point in its development, F has very poor error checking on commands and their arguments, so type carefully or something bad will happen. Feel free to report bugs, or better yet patch the source code (see L below). Index: parrot-svn/docs/parrot.pod === --- parr
