Quote:
Originally Posted by sigma63
Hello Toni,
now i'm playing with the 64bit Version under Win10. 
If i load my program which has two hunks (code & data/bss) with uaedbg, it prints about a third hunk with size 4096 wich i think is for the stack, right? Could this size be configured? |
It is stack and size is taken from program's original stack size. (If you run it from shell, use stack command. I really recommend using larger stack than 4k)
Quote:
Now if i start with "g" i get an illegal-memory-access-error: obviously access to uninitialized stack area.
I think this is due to my use of the SAS/C-Compiler and the linkage with the normal startup-module c.o. This code tries to get the stack-base wich is a (possible undocumented?) parameter on the stack.
|
Attach small example executable, thanks.
Quote:
|
Later i get some Exceptions 8, 26 and 27. I think they are Priviledge-Violation, Int-2 and Int-3. Should i inspect my code for errors or is this normal behavior? I think this happens by printf (DOS-calls, eg. Write).
|
This is just debugger reporting all exceptions/interrupts. (8 = rom uses this to enter supervisor mode). They can be ignored.