similar to: How do I debug com32 modules with GDB using DWARF format?

On 10/10/17 12:11 AM, Gene Cumm wrote: > > I can't say I've ever tried using gdb against COM32 modules. > Well, in syslinux v5.00 and above, com32 modules are effectively built as ELF. Btw, I already found a way, though not perfect: - Create a FAT bootable disk image using "syslinux --install". - Copy hello.c32 module and load it in syslinux.cfg. - Find the

On Thu, Oct 5, 2017 at 11:48 AM, Tu Do via Syslinux <syslinux at zytor.com> wrote: > Hi list, > > I ran a syslinux drive on a QEMU machine with a gdbstub opened. I tried the simplest modules: the hello.c in com32/samples/ directory, which is compiled into hello.c32 in bios/com32/samples/. I already compiled the module with debug info attached via -g option added to CFLAGS in the

Hey guys, I can't seem to figure out how to debug a COM32 app with GDB under qemu. I start "qemu -s" and then "gdb hello.elf ; target remote:1234" but can't set any breakpoints that work. I"m using syslinux4 (pathbased from the repo). Can anyone verify that they can use qemu+com32+gdb with something as simple as com32/samples/hello.c32 ? Also, is it

Hi Everyone, This question might be a long shot, but is it possible to mix and match com32 programs written against Syslinux 3 with com32 programs written against Syslinux 4 without recompiling. We are trying to have our com32 programs run with different versions of Syslinux without modification. Appreciate any advice, thanks in advance.

Dear Syslinux bootloader list, I'm running into a few issues concerning Syslinux modules here, hoping you can answer one or more of the following questions: * Where's "ifmemdsk.c32" ? 4.05, 4.06pre1 and latest 4.10pre seem to lack it. Only the "ifmemdsk.c" file, which is likely sourcecode. Not seeing any "ifmemdsk.cbt" legacy comboot module. * Do COM32

From: Matt Fleming <matt.fleming at linux.intel.com> This series includes a patch (PATCH 1/6) that I sent previously but I thought it was worth sending it again since the rest of the series depends on it, and it also gives a bit of context. These cleanups make it simpler to do the big switchover to ELF modules on the elflink branch because the libraries in $LIBS are now contained in one

Hi all... I'm looking once again at the Syslinux roadmap. It seems to me that we're going to have a very hard time making Syslinux 4.00 be the full-featured everything-in-C release I had hoped for, or perhaps more specifically, that it is justifiable to sit on the current filesystems-in-C code waiting for the rest. That would probably mean productizing the transitional COM32R module

While playing with the current master of Syslinux, I figured out two bugs I'd like to share with you. 1- Missing menu entires If you consider a file with the following entries, only the first item appears label mga32 kernel anything label mga64 kernel anything Looks like the number at the end of the label is giving some headaches to gfxboot. If I do rename this two entries by

Hello ! I am completely new to syslinux. I followed this instruction manually: http://www.wonkity.com/~wblock/docs/html/pxe.html I am on debian and do not have syslinux installed, but using this debian box as a tftp server. I had to modify the instructions given by the installation above. I downloaded the 6.02 version and copied the files to the tftp root. I am using dnsmasq as a tftp

Hey guys, I've searched the archives but couldn't find any instructions on setting breakpoints in com32 apps. I'm trying to debug my app under Qemu. BTW, is there any limits on the amount of malloc space you can do? I'm trying to track down a reboot after a lot of mallocs. Thanks a lot.

Hi there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules

On Wed, Oct 4, 2017 at 11:10 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > FWIW, the _need_ to use linux.c32 is becoming more common (in the sense > that other loading methods are not always capable of loading > newer/current kernels+initrams+additional_files, considering their > sizes). Unfortunately, only a minority of users seem to be aware of > Syslinux's

Hi, I'm working on a com32 module in which I need to get some file size. The only way I found was to include the "lib/sys/file.h" header file and get the i.length field from the file_info structure (once a file descriptor is open). I understand that this structure is internal to the Com32 file I/O implementation and should not be accessed from com32 modules. So is there a

The following changes since commit 4fc3fd1e14f4c1b9208ef262e5b6aef853e9fce4: graphics: make use of syslinux_force_text_mode() (2012-05-19 02:05:38 -0300) are available in the git repository at: git://github.com/aericson/syslinux.git elflink for you to fetch changes up to 2779b713bdd8644ee2b52962ece6daa209b4ba6b: com32: remove duplicate modules (2012-05-22 20:59:51 -0300)

Hello, As it is known, Syslinux loads COM32 modules to 0x101000 (the PM IDT is at 0x100000). Unfortunately, in my project this area of memory is already occupied by another program that I need to preserve for a while (specifically, until Syslinux's COM32 module boots up the OS kernel). In other words, I need to load and execute COM32 modules from other than 0x101000 area of memory (for

Hello all I have installed "syslinux" as follows: Microsoft(R) Windows 98 (C)Copyright Microsoft Corp 1981-1999. C:\WINDOWS>format o: /s C:\WINDOWS>format o: /s WARNING, ALL DATA ON DISK DRIVE O: WILL BE LOST! Proceed with Format (Y/N)?y Checking existing disk format. Formatting 967.98M Format complete. System transferred Volume label (11 characters, ENTER for none)?

On Sun, Sep 20, 2015 at 8:33 AM, syslinux-bot for Gene Cumm <gene.cumm at gmail.com> wrote: > Commit-ID: e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Gitweb: http://www.syslinux.org/commit/e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sun, 20 Sep 2015 08:30:55 -0400 > Committer: Gene Cumm <gene.cumm at

Hello, I have a simple shell script that I use to generate an iso installer depending on the release version that I want. The thing is that I extract isolinux and menu.c32 from the syslinux rpm of the latest redhat release. The reason I am doing it this way is because of the This is what does it: copymenu32() { # $ cat /local/kickstart/templates/os-updates.txt # RedHat-5.8|20120425

Gene, I'm lurking on this issue. Just in general it's fascinating because I basically use syslinux in a monkey-see-monkey do manner. Can you explain why you used the menu entries that way? What they actually do? You mentioned logging... How is the enabled/configured? Inquiring minds want to know and links to docs will do :) On 10/03/2017 03:30 AM, Gene Cumm via Syslinux wrote: >

From: Matt Fleming <matt.fleming at linux.intel.com> This is a series of patches that, * shrink the core by moving things into an ldlinux ELF module * begin wiring up some of the C versions of various functions The core now only contains essential code and loads the ldlinux module to do everything else, like providing a command line interface and loading kernels. The config file parsing