[fpc-devel] Extracting debug-information from fpc-executables
Joost van der Sluis
joost at cnoc.nl
Thu Oct 18 11:45:24 CEST 2007
Op woensdag 17-10-2007 om 13:22 uur [tijdzone +0200], schreef Joost van
> On recent (development) Fedora-systems the debug-information is
> extracted form executables in a different manner.
> That could be a problem when building RPM's on a Fedora system.
> I got this output, does it ring a bell to anyone?
> + /usr/lib/rpm/find-debuginfo.sh /builddir/build/BUILD/fpcbuild-2.2.0
> extracting debug info from /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/lib64/fpc/2.2.0/ppcx64
> /usr/lib/rpm/debugedit: /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/lib64/fpc/2.2.0/ppcx64: Could not find DWARF-2 abbreviation -1
> extracting debug info from /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/bin/plex
> /usr/lib/rpm/debugedit: /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/bin/plex: Could not find DWARF-2 abbreviation 255
> extracting debug info from /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/bin/fpcmake
> /usr/lib/rpm/debugedit: /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/bin/fpcmake: Could not find DWARF-2 abbreviation -1
> extracting debug info from /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/bin/fp
> /usr/lib/rpm/debugedit: /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/bin/fp: Could not find DWARF-2 abbreviation -1
> extracting debug info from /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/bin/rmcvsdir
> /usr/lib/rpm/debugedit: /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/bin/rmcvsdir: Could not find DWARF-2 abbreviation -1
> extracting debug info from /var/tmp/fpc-2.2.0-7.fc8-root-kojibuilder/usr/bin/h2pas
> error: Bad exit status from /var/tmp/rpm-tmp.22914 (%install)
Someone from Redhat helped investigate and solve the problem. There was
one problem with rpm
(https://bugzilla.redhat.com/show_bug.cgi?id=336951) which is fixed.
But there is also a fpc-bug
They updated the rpm-package, so that it doesn't crach on it anymore
(https://bugzilla.redhat.com/show_bug.cgi?id=337011) but I like to have
this fixed in fpc.
But I think I've heard some fpc-developers talking about this issue
before, are the problems with file-names in the dwarf-debuginfo fixed?
And do fpc follow the guidelines as in the bug-report?
More information about the fpc-devel