Re: [edk2] [PATCH v3 1/2] MdePkg: introduce DxeRuntimeDebugLibSerialPort

2018-02-23 Thread Laszlo Ersek
On 02/22/18 20:57, Ard Biesheuvel wrote: > On 22 February 2018 at 19:40, Kinney, Michael D > wrote: >> >> Ard, >> >> In DebugAssert(), if you have deadloop or BP enabled for >> the ASSERT(), then it would be good to have the message >> available in the local variable

Re: [edk2] [PATCH v3 1/2] MdePkg: introduce DxeRuntimeDebugLibSerialPort

2018-02-22 Thread Ard Biesheuvel
On 22 February 2018 at 19:40, Kinney, Michael D wrote: > > Ard, > > In DebugAssert(), if you have deadloop or BP enabled for > the ASSERT(), then it would be good to have the message > available in the local variable Buffer. > > Perhaps only the call to

Re: [edk2] [PATCH v3 1/2] MdePkg: introduce DxeRuntimeDebugLibSerialPort

2018-02-22 Thread Kinney, Michael D
Ard, In DebugAssert(), if you have deadloop or BP enabled for the ASSERT(), then it would be good to have the message available in the local variable Buffer. Perhaps only the call to SerialPortWrite() should be filtered. Mike > -Original Message- > From: Ard Biesheuvel

Re: [edk2] [PATCH v3 1/2] MdePkg: introduce DxeRuntimeDebugLibSerialPort

2018-02-22 Thread Laszlo Ersek
On 02/22/18 19:15, Ard Biesheuvel wrote: > Introduce a variant of BaseDebugLibSerialPort that behaves correctly with > regards to the use of the serial port after ExitBootServices(). At boot > time, all DEBUG() prints and ASSERT() invocations are executed normally. > At runtime, DEBUG() prints are