> On Nov 12, 2014, at 5:49 PM, Jordan Justen <jordan.l.jus...@intel.com> wrote: > > On 2014-11-12 16:22:59, Andrew Fish wrote: >> >> On Nov 12, 2014, at 4:08 PM, Jordan Justen <jordan.l.jus...@intel.com> >> wrote: >> >> On 2014-11-12 15:22:18, Andrew Fish wrote: >> On Nov 12, 2014, at 2:26 PM, Jordan Justen < >> jordan.l.jus...@intel.com> wrote: >> Too bad the DebugAgent isn't actually useful for all the trouble >> it >> causes. :) >> >> 1st question what is wrong with the DebugAgent? Why is int not >> useful? >> >> Last time I looked at it you had to get about 4 pieces of software >> talking together, and half of them were closed source. (For a while, I >> think you needed a separate Windows machine as well.) >> >> Sorry for the stupid question, we don’t use the Open Source >> DebugAgent. > > You mean, you don't use the EDK II DebugAgent bits? I guess that means > you most likely don't use DebugAgent at all?
We have our own implementation of the DebugAgentLib. So we implement the library class. > >> I assumed there would be a Python script to convert to WinDBG to >> gdb-remote. > > Hmm. That sounds horrible. Luckily, *I think* it actually has improved > from this point. I'm not sure though. Well it is just bits… > >> 2nd question why are you using the DebugAgent, >> >> I am not. >> >> when you could just use the QEMU built in gdb stub? >> >> I've put some effort into this. It kind of works. DEBUG works better. >> >> Do you mean DEBUG prints? > > Yep. > >> I think there could be value to using the EDK II DebugAgent solution, >> despite availability of the the gdb stub ... if it was actually easier >> to use than DEBUG. >> >> Are there just not scripts to load symbols with gdb? > > Yeah, I kind of had something for this working. Mode changing kind of > confused things. I think it might useable in some scenarios. > Now you mention it I remember seeing some issue about gdb in that regard. I wonder if you could create a gdb connection, manually send a a packet, use the response from that packet to launch gdb for the correct CPU arch. In lldb we figure out the CPU mode as part of the connect sequence. We can reconnect and reload symbols after a mode change without exiting the debugger. Thanks, Andrew Fish > -Jordan ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
