search for: core_debug

...stances 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 use printf d...

Gene Cumm said on Wed, Oct 28, 2015 at 05:58:59AM -0400: >> Ok, I tried to modify mk/devel.mk to put: >> GCCWARN += -Wno-clobbered -DCORE_DEBUG=1 -DDEBUG_MALLOC -DDEBUG_THREAD >> And removing the -DDYNAMIC_DEBUG but now syslinux doesn't want to build: > >MALLOC and THREAD are two debugs you probably don't want. Ok I can drop them, but that doesn't change the fact it doesn't build :-( >> libcom32.a(bios.o...

...on Wed, Oct 28, 2015 at 01:45:22AM +0100: >> >> Is there a way to increase the debug level of syslinux.efi in order to >> check what it tries to do and diagnose more precisely what happens ? > > > Ok, I tried to modify mk/devel.mk to put: > GCCWARN += -Wno-clobbered -DCORE_DEBUG=1 -DDEBUG_MALLOC -DDEBUG_THREAD > And removing the -DDYNAMIC_DEBUG but now syslinux doesn't want to build: MALLOC and THREAD are two debugs you probably don't want. If you can capture the serial port and the firmware would allow it, "-DDEBUG_PORT=0x3f8" would direct output to...

...M -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 > > to define dpri...

...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, so why is it...

...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 listens to I/O port 0x402 and prints to stdio, add "-debugcon stdio -global isa-debugcon.iobase=0x402" to the QEMU command line. Jonathan Boeing (1): dprintf: add debug console support com32/include/dprintf.h |...

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

Recently had passthrough of 2xPCI DVB-T cards and 1xPCIe DVB-S2 card working, the last know config that was *certainly* working was dom0 xen-4.1.1-3.fc16.x86_64 kernel-3.1.0-0.rc7.git0.0.fc16.x86_64 domU kernel-3.1.0-0.rc8.git0.0.fc16.x86_64 Since then I''ve updated xen-4.1.1-6.fc16.x86_64 on dom0 kernel-3.1.0-0.rc9.git0.0.fc16.x86_64 on dom0 and domU and updated all other packages