tomgracey:

From a casual perusal of the stack dump, it looks like the segfault occurs during cleanup after your code runs. Possibly some things are freed out of order by the libraries and it may not be a serious problem for you. Have you tried putting in some code that does something after the get to see if it works as you expect it to? If everything works and it's just a cleanup bug at the end, you may be able suffer with it (i.e. code your app, report the cleanup bug to the appropriate parties, etc.)

...roboticus

Ah yes...!

Now I see the trap I fell into. My original code indeed had things after the get - it was supposed to write to a file.

I was led astray by the fact the file wasn't generated by the original code. i assumed this went in hand with the segfault. However now I look without blinkers I see it is a permission error preventing the write. ie with tweaking it does in fact run to completion as you suggest.

I never generated a segfault before and it frightened me...

So you are saying I found a bug and this is NOT MY FAULT? Seriously never happened before..!

roboticus - big hat off to you. Great diagnosis, very impressive!