On Nov 11, 2004, at 11:12 AM, Leopold Toetsch wrote:
> Jeff Clites <jcli
...@mac.com> wrote:
>> I'd really like a way to turn them off easily (for the ops as well,
>> actually). I find them to be counterproductive (for our stuff), since
>> what gets shown in the debugger isn't stuff you can actually get gdb
>> to
>> evaluate.
> It depends. While hacking PMC files its much more useful to have the
> gcc
> error line within the pmc files. Debugging ops is sometimes more
> intuitive, if you see the corresponding .c file in the debugger, but
> not
> always.
Sure--definitely depends on what you're doing. For me, I'm often
debugging a JIT problem, and when I end up in a normal-op call I need
to be able to examine the environment (registers, subsequent ops).
> Anyway, as $ENV{PARROT_NO_LINE} is already in ops2c.pl, it should be
> present in all build tools.
Or maybe also CLI options to the tools, so at least you can hand-modify
the Makefile to easily turn off some, and leave on other. Having a
Configure.pl parameter is also more consistent with everything else we
do, compared to an env. variable.
JEff
|
