Your message dated Tue, 28 Jun 2016 15:42:21 +0200
with message-id <[email protected]>
and subject line gdb on ppc64el seems fixed
has caused the Debian Bug report #803363,
regarding [PATCH] notmuch: workaround for FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
803363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803363
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: notmuch
Source-Version: 0.21~rc3-3
Tags: patch
User: [email protected]
Usertags: ppc64el
--
Hi,
on ppc64el, there is a FTBFS on this version since 0.20.2-2 due a test
failing (070).
This is due to the fact that the test is using a breakpoint on the function
notmuch_database_add_message so that it can force a return code and check
the exit code of the binary is the one injected, but for some reason, gdb
fails to trap that function : the breakpoint does not interrupt the program.
In the early days, this was known because of the ABIv2 that makes a function
have a Local Entry Point and a Global Entry Point.
And gdb placed a breakpoint on notmuch_database_add_message, on the address
off the GEP, and in some case you only get through the LEP, and then
the breakpoint is not called.
For reference : https://sourceware.org/ml/gdb-patches/2014-01/msg01013.html
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.
So notmuch is not broken, but there is something wrong with gdb, and
in the meantime, I need to check with gdb what's going on.
F.
---
Index: sources-notmuch/0.21~rc3-3/test/T070-insert.sh
===================================================================
--- sources-notmuch/0.21~rc3-3/test/T070-insert.sh
+++ sources-notmuch/0.21~rc3-3/test/T070-insert.sh
@@ -192,8 +192,9 @@
gen_insert_msg
cat <<EOF > index-file-$code.gdb
set breakpoint pending on
break notmuch_database_add_message
+break *notmuch_database_add_message+8
commands
return NOTMUCH_STATUS_$code
continue
end
--- End Message ---
--- Begin Message ---
Since the test suite for 0.22-1 passed on the buildd, I'm assuming this
bug is fixed for now.
d
--- End Message ---
