Klaus Rudolph wrote:
Joerg Wunsch schrieb:
As Klaus Rudolph wrote:
-C option: provide a "coredump" after simulation finished
Is there a typical format for this?
It's a fairly homegrown (of the old simulavr) text file. I'm
attaching one for reference. Also, it's always using a fixed name.
Changing the format might be an option, though the human readable text
file for sure does have some merit. Right now, avr-libc's testsuite
uses a Python script to extract the desired information (exitcode from
r24/r25, and possibly a message string from "external memory" starting
at address 0x2000). This allows for a fairly simple interface to pass
a result code and possibly a message from the testsuite C source file
to the user.
objdump will do the job as well.
This is WAY overkill if all you want is the exit status. This
is why avrtest has magic ports for exit and abort. You write
the exit code to the exit magic port and poof exit(value) is
called. This is the way all the simulators in gdb work.
I have added these to my tree but haven't cleaned them
up and added documentation yet.
I don't dispute the value of an object dump but it is overkill
for getting exit status values from tool tests.
--joel
_______________________________________________
Simulavr-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/simulavr-devel
