On 04/21/13 19:32, Joe Vernaci wrote: > What would this get you that just using the qemu built-in gdbserver doesn't?
I tried this because it seems to be the official way with -D SOURCE_DEBUG_ENABLE. I suppose the DebugAgent built into the firmware could have more "insight" about the firmware's state. On the debugger side, the UDK debug kit consists of two separate parts actually, the UDK gdb server, and a bunch of python scripts for the gdb frontend, to be used with the edk2 build tree. I didn't get as far as a connected, ready gdb prompt (where I would have loaded the main python script). Maybe I should try the gdb frontend plus the scripts with the qemu built-in gdbserver. Laszlo ------------------------------------------------------------------------------ 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
