mirror of
https://sourceware.org/git/debugedit.git
synced 2026-03-09 03:16:28 +00:00
No description
To make sure the ELF and AR file processed by and created by find-debuginfo are valid introduce a --check-elf[-strict] option. The --check-elf and --check-elf-strict flags will run eu-elflint --gnu on the ELF and AR files before and after processing the files. Including on the generated separate .debug files. When --check-elf-strict is given then if eu-elflint reports any errors find-debuginfo will exit with a failure status. With just --check-elf given any eu-elflint output will be logged but not change the exit status. Add a couple of testcases using --check-elf-strict including minidata, gdb index, dwz creation and an AR file. * configure.ac: Add check for eu-elflint. * scripts/find-debuginfo.in: Add new flags in usage and help. (check_elf, check_elf_strict, elflint_opts, check_elf_msg): New vars. Process --check-elf, --check-elf-struct opts. (do_check_elf): New function. (do_ar_file): Call do_check_elf before/after AR file processing. Propagate return value to caller. (do_file): Check and propagate return value for do_ar_file. Call do_check_elf before and after processing ELF file. Also check debug file. * tests/find-debuginfo.at (FIND_DEBUGINFO_PKG_BUILD_SETUP): Create .o object files. Add tests for --check-elf-strict plus debugdata, gdb-index and dwz. Create ar file from object files and check. https://sourceware.org/bugzilla/show_bug.cgi?id=33827 |
||
|---|---|---|
| scripts | ||
| tests | ||
| tools | ||
| .gitignore | ||
| configure.ac | ||
| COPYING | ||
| COPYING.LIB | ||
| COPYING3 | ||
| Makefile.am | ||
| README | ||
| upload-release.sh | ||
DEBUGEDIT
The debugedit project provides programs and scripts for creating
debuginfo and source file distributions, collect build-ids and rewrite
source paths in DWARF data for debugging, tracing and profiling.
It is based on code originally from the rpm project plus libiberty and
binutils. It depends on the elfutils libelf and libdw libraries to
read and write ELF files, DWARF data and build-ids.
The project home is https://sourceware.org/debugedit/
RELEASES and CODE
Releases are published at https://sourceware.org/pub/debugedit/
To build a release do:
./configure && make && make check
The current debugedit source code can be checked out with
git clone git://sourceware.org/git/debugedit.git
To build a git checkout do:
autoreconf -i -f && ./configure && make && make check
There should be no failures after make check.
BUGS
Please reports bugs at https://sourceware.org/bugzilla/
CONTRIBUTING
The developer mailinglist to send patches to is
debugedit@sourceware.org.
https://sourceware.org/ml/debugedit/
To subscribe send an email to debugedit-subscribe@sourceware.org
Or use the form at https://sourceware.org/mailman/listinfo/debugedit
Please supply patches using git format-patch or using git send-email.
Sign your work
To facilitate tracking of who did what, we've adopted a "sign-off"
procedure for patches based on the procedure used by the Linux kernel
project.
The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right
to pass it on as a patch under the appropriate licenses. The rules are
pretty simple: if you can certify the below:
Developer's Certificate of Origin
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me,
and I have the right to submit the contribution under each
license indicated in, or otherwise designated as being
applicable to, the file.
(b) The contribution was provided directly to me by some other
person who certified (a), and I have not modified it.
(c) I understand and agree that the project and the
contribution are public and that a record of the
contribution (including all personal information I submit
with it, including my sign-off) is maintained indefinitely
and may be redistributed.
then you just add a line saying
Signed-off-by: Random J Developer <random@developer.example.org>
using your real name (sorry, no pseudonyms or anonymous contributions.)
git commit --signoff will add such a Signed-off-by line at the end of
the commit log message for you.
LICENSES
The debuginfo project as a whole can be redistributed under the GPLv3+
as described in the COPYING3 file.
Some individual source files may also be redistributed under the
GPLv2+ as described in the COPYING file or under the LGPLv2+ as
described in the COPYING.LIB file. See the headers of the individual
files to learn which licenses apply. All licenses used are upward
compatible with GPLv3+.