Re: [PATCH 3/6] Facilitate debugging Git executables in tests with gdb
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Oct 27, 2015, 18:09 UTC
- Message-ID
- <CACsJy8C94gzE0CQH=f5=qeMj=DnE3bJ3EnLYbhxgrTG=W4r89A@mail.gmail.com>
- In-Reply-To
- <082d6474a31c405b16087f76de7bc5d01faba529.1445865176.git.johannes.schindelin@gmx.de>
On Mon, Oct 26, 2015 at 2:15 PM, Johannes Schindelin <johannes.schindelin@gmx.de> wrote:
> When prefixing a Git call in the test suite with 'TEST_GDB_GIT=1 ', it > will now be run with GDB, allowing the developer to debug test failures > more conveniently.
I'm very slowly catching up with git traffic. Apologies if it's already mentioned elsewhere since I have only read this mail thread.
Is it more convenient to add a sh function "gdb" instead? Most of the time I only want to stop one command, and I put "gdb /path/..../" in front of "git ...". This gdb function could just expand to that THis would make it a lot more convenient to debug (single command, not full .sh file).
We can even go further with supporting gdbserver function, to launch gdbserver, then I can debug from outside, works even without -v -i.
-- Duy