https://github.com/tromey/gdb-admin

Admin scripts for use with gdb
https://github.com/tromey/gdb-admin

Last synced: 12 days ago
JSON representation

Admin scripts for use with gdb

• Host: GitHub
• URL: https://github.com/tromey/gdb-admin
• Owner: tromey
• License: gpl-3.0
• Created: 2013-11-11T15:15:08.000Z (about 11 years ago)
• Default Branch: master
• Last Pushed: 2014-05-08T14:07:09.000Z (over 10 years ago)
• Last Synced: 2024-10-28T12:42:58.737Z (2 months ago)
• Language: Perl
• Size: 145 KB
• Stars: 2
• Watchers: 3
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
gdb-admin

=========

Admin scripts for use with gdb

merge-gcc-to-src

----------------

This merges shared files from GCC to binutils-gdb.git.

To use this script:

1. Set up a new directory to work in.  Let's call it X.

    mkdir X

2. Check out GCC and binutils-gdb:

    cd X

    git clone ssh://sourceware.org/git/binutils-gdb.git

    git clone ssh://gcc.gnu.org/git/gcc.git

3. Write a "config.pl" file that holds the location.  config.pl

   should be in the same directory as merge-gcc-to-src.

    $SYNC = 'X';

    

4. Find the most recent commit that was passed to the script.

   Normally the script will automatically determine this by looking at

   the "master" ref in the gcc repository, but you have to find it the

   first time.  You can find this commit by looking in

   binutils-gdb.git, finding the most recent sync, and then finding

   the corresponding commit in gcc.git.

5. Now run the script:

    merge-gcc-to-src COMMIT

6. The script will print some output as it works.  When it is done,

   you can look in X/Outputs to see what commits it thinks must be

   merged.  You must usually do this by hand, one commit at a time,

   using "git am".  Sometimes a bit of editing or merging is required.