Experimental Physics and
Industrial Control System

Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> · Thu, 26 May 2022 15:22:39 -0700

On 5/26/22 14:48, Mark Rivers wrote:

Other ideas of how to debug it?

If we accept that the stack trace is correct, then memory corruption
at some earlier point seems likely.  It would be interesting to inspect
the stack of the faulting thread.  However, I don't know if this is
possible with your setup, and wouldn't be able to talk you through it
anyway.

At this point, maybe bite the bullet and go for git-bisect?  This
will likely take some time to work through, although perhaps less than
what has already been spent.

According to git 2.30.2 on my laptop, bisecting 7.0.5 through 7.0.6.1
would take 7 iterations assuming no skips (eg. build failures).

Begin with:

git bisect start R7.0.6.1 R7.0.5

This will update your checkout to a revision for testing.  Build
and run.  If if doesn't build, or the result is otherwise inconclusive,
then 'skip':

git bisect skip

If the problem appears:

git bisect bad

If the problem does not appear:

git bisect good

Each time the checkout will be updated to another revision.  Repeat
until complete.  Ideally this will narrow down to a single revision.
If there are skips, it will give a range of revisions (hopefully
not including a 3.15 merge commit...).

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System