🚀 go-pugleaf

> ...There was another road to try out: bordebug.dll...

I just looked and could not find a bordebug.dll.  Where did you find it?

> ... ever stared at binary data trying to grok its structure? ...

Do I detect a Heinlein fan?

.  Ed

> Helmut Giese wrote in message
> news:4497e6bb.1714921@forums.borland.com...
>
> First I tried analyzing the .obj files. I had found some
> documentation but it turned out to be insufficient. Basically
> an .obj file consists of a suite of blocks which are structured
> like this:
> - 1 byte: key (what type of block)
> - 2 bytes: size of data to follow
> - n bytes of data
>
> So you hop along analysing the content of each block according
> to its type. But invariably at some point the sequence seemed
> broken. Well, it couldn't really be broken, because the linker
> knows how to handle those .obj files, but the sequence didn't
> make sense:
> - you found an unknown type or
> - the size was impossible (leading beyond the actual file size)
>
> So after a week of frustrating work (ever stared at binary data
> trying to grok its structure?) I gave up.
>
> There was another road to try out: bordebug.dll. It contains
> functions which know to analyse a .tds file - but be warned: it
> is no joy to work with.
>
> But if anybody wants to go this route: Get a copy of Delphi
> Magazine Issue 63. It contains an article "The return of the
> giant" which presents a tool (in Delphi, of course) which uses
> bordebug.dll to show you all kinds of information. The sources
> are available online but the article _really_ helps. I strongly
> suggest investing those 7 British Pounds to get a copy.
>
> But still a last warning: You should have an exceptional need
> if you think you need this kind of information - something like
> building your own debugger - otherwise the investment in time
> is ridiculously large wrt to the actual gain.