Nicholas Clark <[EMAIL PROTECTED]> writes:
> On Fri, Aug 22, 2003 at 02:30:13PM +0200, Juergen Boemmels wrote:
>
> > a format for the line-info bytecode segement. The only question is
> > reinvent the wheel, or use an already established format (stabs or
> > DWARF).
>
> can they do the things below?
DWARF has column numbers.
> > It might be nice to have column information to. This would make
> > debugging of Befunge programs a lot more easy. Also it would be nice
>
> I think that it has practical uses for other, dimensionally inferior
> languages. It would often be nice to know which bit of this line:
>
> } elsif ($host =~ /([^.]+\.[^.]{3}$)/ || $host =~ /([^.]{4,}\.[^.]{2}$)/ ) {
>
> generated the undefined warning
Even in C this things happen.
> Also, to be general we should do arbitrary dimensions, else the trifunge
> hackers will feel left out.
But what file-format do they use? Definitifly no plain text file,
because these are normaly 2-dimensional. One can abuse the linenumber
(or the columnnumber) to create an offset in their special file.
If they use text-files there exsits already a mapping from planes to
line/columns, and we can use that.
> > to have blocks of code (many pasm-lines) with just one linenumber, and
> > otherwise have a possiblity to increase the source-line with each line
> > of pasmcode.
>
> Also it would be nice to be able to record debugging lines at several levels,
> so that a macro invocation can be stepped through as one line, or as each
> line of the macro definition. (recursively)
This associates many source-lines to one instruction: The unexpanded
source-line, the first level of expansion, ...
Problem how to create and read out this multi-level
instruction->source-line mapping. A simple #line isn't sufficent any
more.
> It's a right pain trying to follow the perl5 C source in a C debugger, or
> C++ inline code in gdb. I think that we can learn from those pain sources.
Don't repeat errors; make your own errors.
boe
--
Juergen Boemmels [EMAIL PROTECTED]
Fachbereich Physik Tel: ++49-(0)631-205-2817
Universitaet Kaiserslautern Fax: ++49-(0)631-205-3906
PGP Key fingerprint = 9F 56 54 3D 45 C1 32 6F 23 F6 C7 2F 85 93 DD 47
