From stappers at stappers.nl Fri Jan 9 23:04:28 2026 From: stappers at stappers.nl (Geert Stappers) Date: Sat, 10 Jan 2026 00:04:28 +0100 Subject: [ipxe-devel] where to begin debugging Message-ID: Hello, Being a bootloader, that iPXE is, implies starting with nothing. Having nothing means having no debugprintroutines. What is the first console output that iPXE produces? Which DEBUG= to use to follow the program flow? As in: Which .c file contains main()? ( https://ipxe.org/download#debug_builds doesn't tell ) Regards Geert Stappers -- Silence is hard to parse From stappers at stappers.nl Sun Jan 11 21:03:44 2026 From: stappers at stappers.nl (Geert Stappers) Date: Sun, 11 Jan 2026 22:03:44 +0100 Subject: [ipxe-devel] where to begin debugging In-Reply-To: <0102019ba5013e90-636f7892-f383-48c5-a788-c938474da605-000000@eu-west-1.amazonses.com> References: <0102019ba5013e90-636f7892-f383-48c5-a788-c938474da605-000000@eu-west-1.amazonses.com> Message-ID: On Fri, Jan 09, 2026 at 11:04:40PM +0000, Geert Stappers wrote: > > Hello, > > > Being a bootloader, that iPXE is, implies starting with nothing. > Having nothing means having no debugprintroutines. > > What is the first console output that iPXE produces? > > > Which DEBUG= to use to follow the program flow? > As in: Which .c file contains main()? > > > ( https://ipxe.org/download#debug_builds doesn't tell ) > I'm asking for my future self. Would be cool if My future self will find the "where to begin debugging" on the iPXE website or here in the mailinglist archive. It is not only me who does benefit from that knowledge. And it is not my future self that my current self is asking. This was on the iPXE channel on IRC: |21:44 < person> Is there a way how to enable debug for all facilities? |Day changed to 09 jan 2026 |04:21 < stappers> enable debug on all facilities results in being flooded | by debug messages |06:05 < person> stappers: ok ... so what facility do I need to begin with? |06:07 < person> stappers: I need the debug flood just to identify the | facility responsible for the freeze and therefore I | probably don't care it floods the output since I need | just the last messages Groeten Geert Stappers -- Silence is hard to parse From mcb30 at ipxe.org Mon Jan 12 15:55:27 2026 From: mcb30 at ipxe.org (Michael Brown) Date: Mon, 12 Jan 2026 15:55:27 +0000 Subject: [ipxe-devel] where to begin debugging In-Reply-To: References: <0102019ba5013e90-636f7892-f383-48c5-a788-c938474da605-000000@eu-west-1.amazonses.com> Message-ID: <852835cb-9e92-4b41-939e-54e33d2c8a73@ipxe.org> On 11/01/2026 21:03, Geert Stappers via ipxe-devel wrote: >> Being a bootloader, that iPXE is, implies starting with nothing. >> Having nothing means having no debugprintroutines. >> >> What is the first console output that iPXE produces? >> >> Which DEBUG= to use to follow the program flow? >> As in: Which .c file contains main()? main() is in core/main.c (for x86 BIOS or RISC-V SBI builds: UEFI has its own flow with multiple possible entry points). But that's not particularly useful in terms of debugging. > I'm asking for my future self. Would be cool if My future self > will find the "where to begin debugging" on the iPXE website > or here in the mailinglist archive. If the starting point is an iPXE error message, then the error page already includes suggestions of which DEBUG options to attempt first. Michael