Currently there are a few instances where x86 specific assumptions/code are
used [1] in what I consider as the target agnostic level of fpdebug. My
proposal is to move these instances to a hardware target specific unit so
that these target specific handling is clearly separated. One location for
On 16/12/2021 12:10, Christo Crause via lazarus wrote:
One location for the target specific code is perhaps the fpdbgdisas*
units, since it already provides a number of hardware specific
concepts such as identifying call & return instructions and some stack
frame analysis. Adding for example
Ok, for now limiting this to a smaller audience, to get some
brainstorming done.
=> Original mail at the bottom.
Some initial thoughts.
*** First, I would suggest, that all calls go to T[Foo]DbgProccess ***
T[Foo]DbgProccess can then forward them.
Outside classes should not have knowledge, nor
Martin Frb via lazarus schrieb am Do., 16.
Dez. 2021, 23:27:
> Only, question is, if we need the ABI?
> - Do win64 and linux64 share the same ABI? (or win32 <> linux32)?
>Afaik SEH is win specific (and probably would be best of in the ABI?).
>But there could still be a base class that is
