Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #55967

Re: DWARF debugging information, and FORTH

Show all headers | View raw

On 2017-03-19 8:42 PM, hughaguilar96@gmail.com wrote:
> On Sunday, March 19, 2017 at 4:55:31 PM UTC-7, Walter Banks wrote:
>> A lot of the open source tools lose details of the original source
>> structure. To Hugh's point single stepping at the instruction
>> level is not worth much be it forth or C. Elf/Dwarf as I have found
>> is fully capable of being used at the original language level
>> (including stepping at language statement level) with links back to
>> the source not the generated code.
>
> What??? You thought I was displaying a disassembly of the generated
> code? That is only done when the source-code isn't available --- the
> only people who don't have source-code are software pirates.
>
> My debugger was source-level. As I said before, the compiler compiled
> a BRK between every Forth word compiled (some compiled as a JSR and
> others compiled as inline machine-code). The compiler also built a
> data-base of where all of these BRK instructions were in the
> machine-code and where the compiler was in the source-code at the
> time (I used UR/Forth's dictionary to do this; it was a hash-table
> and was pretty fast). When the BRK occurred on the 65c02 the ISR
> would send a message over the RS232 to the host and tell it all the
> pertinent info about the situation (where the BRK was, what the
> values of the registers were, and what the top few items on the
> data-stack were). The debugger would then display the source-code
> with a smiley-face character blinking at the location in the
> source-code. Also, on the bottom of the screen were displayed the
> register contents and the top few items on the data-stack. I may have
> also displayed my local variables --- I can't remember --- that was
> 25 years ago. I could also set break-points and watch-points,
> although I didn't use these very much. The whole thing was modeled
> after Borland Turbo Debugger that I was familiar with at the time.
>

At its lowest level ELF/DWARF has instruction level information to
execute an instruction at a time. There is also can be information to
step at the level of the source code statements.

As I pointed out in the original post definition and implementation
issues are a problem in source level debugging with ELF/DWARF. It
certainly is widely used.

Current debugger technology doesn't generally used compiled in
statement delimiters (like BRK) even ion code executing from ROM.

w..

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

DWARF debugging information, and FORTH stoyan.shopov@gmail.com - 2017-03-17 16:20 -0700
  Re: DWARF debugging information, and FORTH rickman <gnuarm@gmail.com> - 2017-03-17 19:55 -0400
    Re: DWARF debugging information, and FORTH hughaguilar96@gmail.com - 2017-03-17 20:31 -0700
      Re: DWARF debugging information, and FORTH stoyan.shopov@gmail.com - 2017-03-18 01:04 -0700
        Re: DWARF debugging information, and FORTH hughaguilar96@gmail.com - 2017-03-18 01:38 -0700
          Re: DWARF debugging information, and FORTH stoyan.shopov@gmail.com - 2017-03-18 04:44 -0700
  Re: DWARF debugging information, and FORTH Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-18 03:51 -0500
  Re: DWARF debugging information, and FORTH Walter Banks <walter@bytecraft.com> - 2017-03-19 19:55 -0400
    Re: DWARF debugging information, and FORTH hughaguilar96@gmail.com - 2017-03-19 17:42 -0700
      Re: DWARF debugging information, and FORTH Walter Banks <walter@bytecraft.com> - 2017-03-20 11:48 -0400
        Re: DWARF debugging information, and FORTH hughaguilar96@gmail.com - 2017-03-20 16:53 -0700
      Re: DWARF debugging information, and FORTH Walter Banks <walter@bytecraft.com> - 2017-03-20 15:13 -0400

csiph-web