Differences between revisions 19 and 20
Revision 19 as of 2012-11-05 23:34:23
Size: 4566
Editor: brobecke
Comment: Additional instructions on how to update our gnulib import.
Revision 20 as of 2013-03-16 11:33:49
Size: 4579
Editor: 195-240-174-60
Comment: how is anyone supposed to grab this script? it says i'm not allowed to attach, whereas i just want to _see it
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
  The [[attachment:mklog.pl|mklog]] script creates a !ChangeLog template for a diff file. This version was written by Diego Novillo and updated by Daniel Jacobowitz. Run "mklog diff-file" and the template will be added to the top of the file.   The inaccessible [[attachment:mklog.pl|mklog]] script creates a !ChangeLog template for a diff file. This version was written by Diego Novillo and updated by Daniel Jacobowitz. Run "mklog diff-file" and the template will be added to the top of the file.

List of requirements for patches

The file <gdb-src>/gdb/CONTRIBUTE contains instructions on what is expected from patches submitted to GDB. Please read through that document, and pay special attention to the Coding Standard and ChangeLog requirements.

GDB Internals documentation

GDB has an official Internals Manual (see the documentation page). It is a good reference guide for GDB, but some parts are incomplete or outdated.

Jeremy Bennett wrote Howto: Porting the GNU Debugger, which is a good source of information as well. It is primarily aimed at engineers who will port GDB to a new target for the first time, but contains an overview of GDB Internals that is of general interest.

Creating ChangeLog entries

  • The inaccessible mklog script creates a ChangeLog template for a diff file. This version was written by Diego Novillo and updated by Daniel Jacobowitz. Run "mklog diff-file" and the template will be added to the top of the file.

Editing configure.ac

After editing gdb/configure.ac, you need to regenerate gdb/configure, gdb/config.in and gdb/aclocal.m4:

$ pwd
/path/to/src/gdb
$ aclocal -I gnulib/m4
$ autoconf
$ autoheader

Please note:

  • You need to use the correct versions of aclocal, autoconf and autoheader. The correct version is the one mentioned at the beginning of gdb/aclocal.m4 and gdb/configure.

  • Don't include the changes to these generated files in your patch when you post it to the mailing list. These files are big and unnecessary for code review.

Updating GDB's import of gnulib

GDB now imports various modules from the gnulib project, located in gdb/gnulib. This import is used when building both GDB and GDBserver.

To facilitate the update of our import, a script called update-gnulib.sh has been created to automate the process. To run this script:

    % cd /path/to/gdb-sources/gdb/gnulib
    % ./update-gnulib.sh /path/to/gnulib-git-repository

When run without change, the new import should be identical to the previous one. This is actually a good test to perform before making any update to our import, to make sure that everything is correctly setup.

The script maintains the two key pieces of information from which the import is created as constants defined inside the script:

  • GNULIB_COMMIT_SHA1 - which commit from the gnulib respository is to be used for the import;

  • IMPORTED_GNULIB_MODULES - which modules to import from gnulib.

When updating the import, please only modify one element at a time. For instance, if you want to import a new module only defined in a later version of gnulib, please first update the import to use the newer commit as a first patch, and then update the import to include the new module as a second patch.

Patch Tracker

gdb has a patch tracker. Read here for instructions on how to use it.

Debugging gdbserver on Linux

GDB has issues with breakpoints set in gdbserver. Ulrich Weigand has a tip to make it work:

Gdbserver uses a direct call to the Linux "clone" system call at startup,
and for some reason GDB gets really confused by this.

When I want to debug gdbserver, I generally simply comment out the call
to linux_test_for_tracefork in linux-nat.c:initialize_low to avoid this.

Writing testcases

See GDBTestcaseCookbook.

Finding Gnats bug entries in the Bugzilla database

If you ever had to find an old bug in the Bugzilla database, you probably stumbled upon this situation. There are some old entries from the now-retired Gnats database, which can be found by:

  • Adding 7105 to the Gnats bug number;

  • Search for "Converted from Gnats NNN", where NNN is the Gnats bug number.

  • Use "gdb 123" Location with Mozilla bookmark keyword "gdb", URL "http://localhost/~user/cgi-bin/buggdb.php?id=%s" and install this file as "~/public_html/cgi-bin/buggdb.php".

None: DeveloperTips (last edited 2014-03-31 17:41:37 by DougEvans)

All content (C) 2008 Free Software Foundation. For terms of use, redistribution, and modification, please see the WikiLicense page.