search for: debug_stdio

...e has three instances of "!PXE" in the chunk of memory that "Method D" should look at. I thought I would try to find out how pxelinux copes with this, by trying to insert printfs in pxe_init, but nothing gets printed. I can spew lots of output if I set DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 but given that this box doesn't have a serial port, anything I add will whizz off the screen. >From looking at com32/include/dprintf.h, it looks as though all this does is to define dprintf to printf, so why is it that if don't define DEBUG_STDIO and CORE_DEBUG, and just...

...handle > instead. That's weird, since enabling this finally got me some debugging output from dprintf(). I think I'm being lucky here! HP apparently provides the necessary glue. What would be the correct way to enable debugging under EFI? Normal printf output remains invisible, so DEBUG_STDIO doesn't work. If there is nothing yet, I think a wrapper around printf (and *prinf) is needed. This should [v]sprintf() to a buffer and then print the resulting buffer using APrint("%a", buffer) if EFI_BUILD is defined.

...5 at 03:20:08PM -0400, Gene Cumm wrote: > > I thought I would try to find out how pxelinux copes with this, by trying > > to insert printfs in pxe_init, but nothing gets printed. > > This is normal. Can you give me hint as to why setting > > DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 changes that state of normality? (AFAICT dprintf.h defines dprintf to printf, so why wouldn't using printf directly work? printf.o gets built regardless of DEBUG settings AFAICT.) > > From looking at com32/include/dprintf.h, it looks as though all this does is > > t...

I noticed several issues when diagnosing why pxechn.c32 didn't work in 5.01-pre3. 1) pxechn.c32, prdhcp.c32 and other modules crash Syslinux and force a reboot by executing an unresolved symbols. unload_pxe(), dns_resolv() and pxe_call() are the three. "Error: An undefined symbol was referenced" 2) In past versions, I built a debug build by having "CFLAGS += -DDEBUG=1"

This patch adds support for printing messages through a debug console. QEMU, for example, supports this through the debugcon facility. The benefit is that it's *much* faster than printing over a serial port. To print to I/O port 0x402 (the default used by SeaBIOS and OVMF), add "-DDEBUG_IO_PORT=0x402 -DCORE_DEBUG=1" to the build CFLAGS. To enable a debug console in QEMU that

...erwriting each other. 2) Method D is quite the fall back. > I thought I would try to find out how pxelinux copes with this, by trying > to insert printfs in pxe_init, but nothing gets printed. This is normal. > I can spew lots of output if I set > > DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 > > but given that this box doesn't have a serial port, anything I add will > whizz off the screen. Serial or some sort of IP KVM with logging is ideal. > From looking at com32/include/dprintf.h, it looks as though all this does is > to define dprintf to printf,...

On 05-08-15 12:05, Gene Cumm wrote: > > I recompiled with this in mk/devel.mk <http://devel.mk>: > > GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 > > 0x2f8 is a BIOSism. Is this a problem? The example in the comments said 0x3f8 which is COM1.

...order some hardware for that, but this > also works very well. A pity I didn't think of using it earlier. > <<< > > You can set the com address for debugging (com1/com2/ whatever) if you like I was originally looking for a way to debug to the console instead. Defining DEBUG_STDIO did not help. Now I know why. > Are you still loading PNGs? > Have you tried vesamenu w/o a background image? No and yes. I removed all fancy stuff, leaving just: LABEL linux KERNEL path/to/vmlinuz IPAPPEND 3 APPEND initrd=path/to/initrd rdblacklist=nouveau MENU LABEL ^AUTO...

Hello Geert Thanks for replying.. But i think i can?t use it, as i don?t reach the point where the debug module will be available.. it just pulls the lpxelinux.0 and tries to get the next download-- the ldlinux.c32 and it fails...and freezes. And the next step would be other modules i think.. if i?m wrong.. excuse me 8-).. yesterday i managed to get ipxelinux working from ipxe.org.. so the nic

On 04-08-15 17:38, Oscar Roozen wrote: > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. I was busy adding some code to dprintf.h