This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH5 PR gdb/16959] gdb hangs in infinite recursion
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Wei-min Pan <weimin dot pan at oracle dot com>
- Cc: Simon Marchi <simon dot marchi at polymtl dot ca>, gdb-patches at sourceware dot org
- Date: Mon, 2 Apr 2018 06:44:26 -0700
- Subject: Re: [PATCH5 PR gdb/16959] gdb hangs in infinite recursion
- References: <20cf4b23322670e4dc513183ef2dda45@polymtl.ca> <96ab9fda-2c03-a9c6-1da9-70e807e69e5c@oracle.com> <3505af0b-d303-b556-0a4c-c416ac88a064@polymtl.ca> <337f2b1f-6fe8-07f3-f4cd-a9b5a3d5456d@oracle.com> <20180330225218.fqhgvt7pzaqewic3@adacore.com> <0bb09bd9-812c-0665-3112-353c0e9cef0e@oracle.com> <20180330234143.mtj7u2xcfi7oxli4@adacore.com> <8c729b8f-24db-c746-e0e6-744ca7edd92f@oracle.com> <20180331015242.zndajxnpmpieltto@adacore.com> <79789d48-f0d3-7a76-f22d-6db52e780389@oracle.com>
> Sorry, I lost the output. But I did resolve the merge conflicts by modifying
> the
> ChangeLog files. I just did a "git rebase --continue" which I didn't do
> before
> and it points to my branch and shows my patch:
>
> % git add ChangeLog
> % git add testsuite/ChangeLog
> % git rebase --continue
> % git commit --amend
> % git show
>
> But when I tried to push again, I got the same "non-fast-forward" error as
> if no merges were ever done.
This is most likely because someone pushed a change between the moment
you fetched + rebased, and the moment you tried to push the rebased
result. You're going to have to redo it again, I'm afraid. Once you
learn to handle those merge failures quickly, this will almost never
happen.
--
Joel