Closed mpickering closed 2 years ago
Probably the more useful thing would be steps you used to cause the crash. It might also help in fully explaining #19.
I am not sure it would be very enlightening because I don't think I could write the transforms to implement #19.
I'm more concerned with the crash at this point really. If you can say how you arranged the transform(s) that caused the crash, that would be helpful. The .dmp may be useful too, but usually a description of the steps to reproduce is more useful.
Where can the .dmp
files be found? I've seeing similar issues.
Graphia doesn't generate any crash dump files, though it does send info to a centralised server which we can see. If it's a severe crash this doesn't always work in which case you might need to start Graphia using a debugger to get any sensible diagnosis.
Having said all that, a bunch of crash bugs have been fixed since 2.2 was released; you might want to try a dev build (https://graphia.dev/). At some point we will update the main public build but for... complicated reasons, we can't right now.
Ah, I understand now! (For some reason, I was thinking how Java generates its own dump files).
I see my coredumps in coredumpctl list
output now. Happy to share wherever. Also, will give dev build a try.
I was trying to do some more complicated things with "apply repeatedly" transformations which made Graphia segfault.
I can email the
.dmp
file to someone if you are interested.