Building OVMF with -D SOURCE_DEBUG_ENABLE is involved. Without -D
SOURCE_DEBUG_ENABLE I get a register dump on the qemu monitor and then qemu
exits (as my app terminates). (not really useful) I'd prefer that gdb
(which is attached via -s and can ctrl-c to break into OVMF) catch this
exception - as that's hopefully where the symbols will be. Would inserting
int 3 (in the right place in the register dump function) but that seems
redundant and likely to cause a double fault...
Alternatively, using -D SOURCE_DEBUG_ENABLE with a proper qemu serial port
connection might suffice, but with the following qemu options (and others
I've tried) I don't get any indication that the debugger has been activated
and responds to keystrokes in the qemu window...
$ /usr/local/bin/qemu-system-x86_64 -m 1024 -bios OVMF.fd -monitor stdio
-vga std -device e1000,netdev=net0,mac=52:52:00:12:34:01 -netdev
type=tap,id=net0,ifname=tap1,script=no,downscript=no -net dump,file=a.pcap
-serial vc:800x600 -S -s
qemu: 1.4.0
gdb 7.5.1
EDK2 tree 14301
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
