On Sat, Dec 10, 2016 at 02:25:08AM +0100, Mattia Rizzolo wrote: > On Fri, Dec 09, 2016 at 08:11:54PM -0500, Bill Blough wrote: > > > >Or does anyone have other suggestions? > > I have one: please try to CC people (and/or MLs) sooner. I now noticed > that you asked for help more than one month ago, but I wasn't aware of > that at all. And now the freeze is hovering upon us.
Yes, fair enough. That's my mistake. > > > In the mean time, would it be possible to get a > > stack trace showing the exception thrown by any one of the test > > programs? > > I got a build in the s390x porterbox, and reproduced the failure; at > least, near enough, mine says > diff test-results.log ./scripts/sanityTest_ExpectedResult.log > Binary files test-results.log and ./scripts/sanityTest_ExpectedResult.log > differ > Makefile:950: recipe for target 'check' failed > Instead of actually showing the diff. > > I'm happy to provide stacktraces and/or core dumps if you can tell me > how to get them without me needed to figure things out. After the build completes, from the build root, run libtool --mode=execute gdb --args samples/SAXCount samples/data/personal.xml At the GDB prompt, type catch throw then run It will stop, saying exception thrown. To generate the stack trace, type bt full There will likely be several screens of data. If you could please copy/paste them all. Once you're back at the gdb prompt, that's the end of that trace. Because there may be multiple exceptions thrown (including as part of normal operation), I'd appreciate a stack trace of all of them. Unfortunately, I don't know how many there will be. On my (working) system there's only one before successful completion. Hopefully there won't be much more than two on the failing system, but depending on the failure there could be several. >From the gdb prompt, typing continue will continue execution until the next exception, at which point you can repeat from the "bt full" step above. Once you get a message saying the process exited, it's done, and you can exit by typing quit This will hopefully help me to isolate this issue. Thanks for your help. Bill
