| commit | 042780801c9ca765b633acc9dc7aebfa649fdbb1 | |
| author | Pádraig Brady <P@draigBrady.com> | |
| Sun, 8 Dec 2013 21:43:49 +0000 (8 21:43 +0000) | ||
| committer | Pádraig Brady <P@draigBrady.com> | |
| Mon, 9 Dec 2013 09:28:29 +0000 (9 09:28 +0000) | ||
| tree | 3bb1a0e270beb8cc4ddc3b48a860a750c74032a2 | treesnapshot (tar.gz zip) |
| parent | 402e8ecbc4bf3b3fe866338e77e21feceac910f0 | commitdiff |
tests: fix false failure due to gdb inline function handling
Inline functions are awkward to breakpoint as mentioned at:
https://sourceware.org/bugzilla/show_bug.cgi?id=10738
The normal case here was for the breakpoint on the inline function
to fail, resulting in a 10s delay before skipping the test.
However on GCC 4.7.2 on ppc64 at least it was seen that
the test failed erroneously due to the breakpoint being successfully
set on an "out of line" function, but an inline function was
actually being called.
* tests/tail-2/inotify-race.sh: Switch to a line based breakpoint,
rather than a symbol base one, which avoids issues with breakpoints
on inline functions. Also skip_ on the initial breakpoint check
in case the breakpoint is not traversed which would be the case
on remote file systems for example.
Inline functions are awkward to breakpoint as mentioned at:
https://sourceware.org/bugzilla/show_bug.cgi?id=10738
The normal case here was for the breakpoint on the inline function
to fail, resulting in a 10s delay before skipping the test.
However on GCC 4.7.2 on ppc64 at least it was seen that
the test failed erroneously due to the breakpoint being successfully
set on an "out of line" function, but an inline function was
actually being called.
* tests/tail-2/inotify-race.sh: Switch to a line based breakpoint,
rather than a symbol base one, which avoids issues with breakpoints
on inline functions. Also skip_ on the initial breakpoint check
in case the breakpoint is not traversed which would be the case
on remote file systems for example.
| tests/tail-2/inotify-race.sh | diffblobblamehistory |