search for: ddebug_stdio

...15 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...

...le 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...

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

...verwriting 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,...

...m 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? What commit ID or numerical version? -- -Gene

...ave no luck. Still I get random Exceptions or reboots shortly after displaying 'My IP is...'. However(!) I did see attempts at loading ldlinux.e64 and more in the logs. What would be the easiest way to enable some tracing except for redefining Print, dprinf and ddprintf? Just defining -DDEBUG_STDIO did not produce anything more than what I have now: "My IP" + crash. I can capture console output through ipmiconsole, so the more verbose I can get it, the more information to grep through.

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"

...iPXE to grab pxelinux.0 or lpxelinux.0 (the former should be safer but the latter should also work). With printf() living in ldlllinux.c32, I'm not sure what can be done at this time. Using the following likely won't work as a result: GCCWARN += -DUNDIIF_ID_DEBUG=0x80U -DLWIP_DEBUG -DDEBUG_STDIO -- -Gene A: Because it messes up the order in which people normally read text, especially the archives of mailing lists. Q: Why is Top-posting such a bad thing? > -----Urspr?ngliche Nachricht----- > Von: Syslinux [mailto:syslinux-bounces at zytor.com] Im Auftrag von Geert Stappers > G...

On 05-08-15 15:28, Gene Cumm wrote: >>> 0x2f8 is a BIOSism. > >> Is this a problem? The example in the comments said 0x3f8 which is COM1. > > It means that a BIOS IO port for a UART won't work for EFI. No value > for DEBUG_PORT will do anything unless someone's got some translation > "glue" to take the attempts to open the UART and use an EFI handle

On Fri, Jul 31, 2015 at 12:37 PM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: >>>> > > 5) upload handles.txt somewhere > > It's waiting at http://okkie.nu/tmp/handles.txt > <<< > > > OK your HP has 4 NICs > > DevicePath(0x0,0x0)/MAC(ECB1D775E524,0x0) > DevicePath(0x0,0x1)/MAC(ECB1D775E525,0x0)) >

...> 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 the first serial port. "-DDEBUG_STDIO" may be useful but by the looks of it, not until after ldlinux.* is loaded as printf()'s code isn't in the core but ldlinux.*. > ranlib liblpxelinux.a > ld -m elf_i386 -Bsymbolic -pie -E --hash-style=gnu -T > /root/syslinux/core/i386/syslinux.ld -M -o ldlinux.elf ldlinux.o \...

Hello Thomas, Thomas Schmitt via Syslinux said on Sun, Oct 25, 2015 at 04:35:57PM +0100: >I assume you can boot Fedora Live CD on the same (virtual) hardware. Not sure for Fedora, but the system is installed with either RHEL6, RHEL7 or Ubuntu 14.04 depending on the Lab I'm making on it without issue. >Just to make sure that the firmware works so far. Globally they do ;-) >