Frederic Bonnard <[email protected]> writes: > This should be fixed in gdb now, but it seems there's an issue on that. > So the workaround for the moment is to place a 2nd breakpoint on the LEP, > which is at the address of notmuch_database_add_message + 8. > On other architectures, this won't cause trouble as the first one will be > activated and return with the forced exit code will be done.
I tested with gdb 7.10-1 on amd64, and that seems not to be the case. All of the tests end up exiting 255 instead of 0 or 1. I didn't have time to dig deeper than that yet. d
