Testing (or trying to test) 64bit addresses for debugging, I'm not able to produce code with such addresses..... Am I doing something wrong ? For now impossible to use all the available memory directly (without using allocate I guess) Waiting comments :-) No problem assembling/linking/execution dim ...

Hi ITomi
Put the -exx option when compiling to trap some reasons of crash (null pointer, out of bound,...)

@juergen I though about the 64 bit issue with stabs. It can be easily fixed. Just by a prog that reads the asm file with stabs data and writes a new one containing the same data but with 64bit adresses. In the example/test below I changed some stabs lines and data can be retrieved in 2 special secti...

If you go the "c way" (.bas to .c) fbc does add the required dwarf info for both 32 and 64 bit. Did i get this right ? Partially true : fbc just adds instructions like this : #line 24 "dbg_test_stack_64.bas" to indicate the original line number and name of the .bas file. The oth...

@Juergen I'm a bit disappointed as I explained twice how it's working. ;-) Gas is always used at the end (at least before the linker). What changed is the format of the debugging instructions it receives and handles. bas --> FBC --> asm + stabs instructions --> GAS --> exe + stabs sections (32bit de...

@St_W Thank you. I haven't investigated your changes in more detail yet, but from looking at the code while applying the changes i think there might be some adaptations required before this can be merged. Just curious, what adaptations do you think about ? Initially to have a more readable code I al...

Hi all, When debugging a source code with include files only lines inside procedures are correctly associated with their file.... I searched in the compiler to find a way to change this behaviour. I did it with very few modifications (#20 lines added or changed). Nota 1 If every include file name is...

Hi ITomi, Sorry not be clear, that's my fault to consider everyone has the same skills..... :-) - The define is at the beginnig of source code, line 31 : #Define MAXSRCSIZE 500000. Changing by 700000 should be ok. - The -t parameter is for compiling fbdebugger : fbc -s gui -t 2048 "FBdebugger.b...

Hi ITomi, Try by adding a sleep statement inside the inkey loop like this : While Inkey <> "":Sleep 100: Wend Obviously if ESC key is pressed a long time it doesn't work. In this case more code is needed to check if the program is returned in the main menu and so on. I tried with the examp...

I had to cheat a bit for executing with FBdebugger but I found a bug when you load images. The size of the image tuz is 224 x 42 but you get 18 x 14 times = 254 therefore out of the width. Change with the code below. x2 is defined without initializer just add the width less one to x1 before the get ...

I just changed my PM address so maybe the issue.
Anyway use debug@aliceadsl.fr

You should also check again the file names in your code including path ;-)

Hi ITomi,

After compiling with -exx you should run the exe by command line to see an eventual error.

Are you compiling in 32bit or 64bit ?

if you don't mind send me by PM your source code and every needed data or a link for downloading I'll try on my side.

Hi ITomi, Currently the size of the buffer for loading each source code is 500 000 bytes. Only one file bigger than that is not well ;-) To fix the loading problem, 2 ways : - increase MAXSRCSIZE (at the beginning of fbdebugger) like that #Define MAXSRCSIZE xxxxxxxx 'max source size a larger value c...

I would pass the wished index as another parameter and no need ptr

Hi all,

It's been a long time since I had to make a new version, however not a lot of new features, see first post. Version 2.92.

http://users.freebasic-portal.de/sarg/fbdebugger292.zip