@St_W thanks for your reply.
By the way I forgot a word in a previous post : "I did my best but I can
not do miracles. Not the same meaning....
Some complements :
- In every case fbdebugger extracts the data from the exe, directly if stabs or via objdump if dwarf (directly would be too complicated). Nothing comes from source codes except the code itself.
- With gas (32 default) the debug data is close from the bas code (line number, and anything alse) so the debugging is fully operational.
- With gcc the translation in C is not always 1 for 1. So there are cases where the debug data doesn't match the initial basic lines or variables.
And a diagram, not as good as fxm's ones.
Code: Select all
bas
|
---
FBC
---
|
-----------------------------------------------------
| |
asm + stabs instructions C code + #line/file instructions from bas code
| from bas code |
| (line number, variables) ---
| (structures, etc) GCC 32/64bit
| ---
| |
| ------------------------------------------
| | |
| asm + stabs instructions asm + dwarf instructions
| | from C code | from C code
| | |
-------------------------------------------------------------------
|
---
GAS
---
|
exe + stabs or dwarf data embedded
|
----------
Fbdebugger :-)
----------