On 04/11/13 16:49, Duane Voth wrote: > With DEBUG_VERBOSE on and -debugcon file:debug.log -global > isa-debugcon.iobase=0x402 added to the qemu command line, debug.log > remains empty. I've never seen any debug output from this flag nor via > -debugcon. My OVMF build line is: > > $ build -D SOURCE_DEBUG_ENABLE -D FD_SIZE_2MB -D DEBUG_ON_SERIAL_PORT -p > OvmfPkg/OvmfPkgX64.dsc -a X64 -t GCC46 > > (when I add other debug code and rebuild, I do see the changes in gdb so > I'm not missing something obvious)
In general I'm dumbfounded, just one note: unless I'm misunderstanding your email, the above is incorrect. I'm under the impression that you use all of the above together at once, ie. (i) the "-D DEBUG_ON_SERIAL_PORT" edk2 build option, (ii) the DEBUG_VERBOSE bit in OvmfPkgX64.dsc::gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel, (iii) the "-debugcon file:debug.log" and "-global isa-debugcon.iobase=0x402" qemu command line options. Again, I may be misunderstanding you, but if this is the case, then (i) and (iii) conflict in logic. (i) makes OVMF print DEBUGs to the serial port, while (iii) makes qemu capture messages written by the guest to ioport 0x402. So, what happens if you drop (i), and keep (ii) and (iii)? (Sorry if that's what you're already doing.) Thanks 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 [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
