<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Dec 11, 2017 at 10:28 PM, Alberto Zin <span dir="ltr"><<a href="mailto:alberto.zin@gmail.com" target="_blank">alberto.zin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div>for some reasons I'm not yet able to investigate in detail, this release 2.4.4 of purr-data broke something on my system.<br></div>Many of my past patches, when opened present a "segmentation fault" error.<br></div></div></div></div></div></div></div></div></blockquote><div><br></div><div>This sounds like a rogue external to me. To check this, reset the preferences (after backing them up), as explained here: <a href="https://agraef.github.io/purr-data-intro/Purr-Data-Intro.html#resetting-the-preferences">https://agraef.github.io/purr-data-intro/Purr-Data-Intro.html#resetting-the-preferences</a></div><div><br></div><div>If Purr then runs normally, it must be one of the externals you added. You may then start re-adding your local externals one by one until Purr crashes again, at which point you will have identified the culprit, and can report the problem on the bug tracker of the corresponding project.</div><div><br></div><div>Otherwise, it may be a bug in Purr, or, equally likely, a misbehaving build. Since you're running my packages, you can check whether you can reproduce the problem with Jonathan's package (as you're running Trusty, that would be <a href="https://github.com/agraef/purr-data/releases/download/2.4.5/pd-l2ork-2.4.5-ubuntu_14.04-x86_64.zip">https://github.com/agraef/purr-data/releases/download/2.4.5/pd-l2ork-2.4.5-ubuntu_14.04-x86_64.zip</a>). These are produced in different ways on different systems, so a packaging bug might show up up in one but not the other.<br></div><div><br></div><div>If only one of the alternative packages exhibits the problem then it's clearly a packaging bug which you should report to the package maintainer (that would be me if only the JGU package appears to be borked; I have a bug tracker for packaging bugs concerning the JGU packages here: <a href="https://bitbucket.org/l2orkubuntu/l2orkubuntu.bitbucket.org/issues">https://bitbucket.org/l2orkubuntu/l2orkubuntu.bitbucket.org/issues</a>).</div><div><br></div><div>If neither of the packages work for you, then you might have hit a bug in Purr, or a platform-specific issue which should be reported at <a href="https://git.purrdata.net/jwilkes/purr-data/issues">https://git.purrdata.net/jwilkes/purr-data/issues</a><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div></div>My simple question is; in order to debug the issue and report something useful to the issue tracker on github<br></div>do I need to build a purr-data version myself with the debug flags enabled? <br></div></div></div></div></div></div></blockquote><div><br></div><div>That would be a lot of hassle. The first thing I'd try is to boil the issue down to a Pd patch as simple as possible and attach that to your problem report. Your bug report should describe the problem and the exact steps needed to reproduce it. A log of what you see in the terminal when you launch Purr from the command line may also be helpful. Then someone from your friendly developer team will hopefully be able to figure it out. ;-) If we can't reproduce the problem then we'll get back to you and ask for more information.</div><div><br></div><div>There are also ways you can run Purr inside gdb (using the "Purr Data DEBUG" icon), which will hopefully give you a backtrace (use gdb's bt command after Purr crashed) which you can attach to your bug report.<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><div></div><div>Any simpler ways like high verbosity level when opening a patch or similar?<br></div></div></div></div></div></div></blockquote><div><br></div><div>Yeah, there's a global -verbose option for that, but last time I checked it could easily cause troubles by itself. There are other ways to go about debugging certain issues once we know what happens where and when, but Jonathan can give better instructions on these. In any case, all of this is best discussed on the bug tracker so that we have a complete trail of the process and don't have to go digging through ml archives...<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><div></div></div><div>Since I have a lot of GoP on my patches I suspect that it is something related to this.<br></div></div></div></div></div></blockquote><div><br></div><div>Then you submit that patch, or preferably a suitably boiled-down version, in your bug report.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div></div><div></div>I'm on Linux Mint 17.3 - 64 bits (based on Ubuntu 14.04).<br></div></div></div></div></blockquote><div><br></div><div>That might also be part of the issue, if Mint uses libraries which aren't binary-compatible with what's on stock Ubuntu. (I consider that unlikely, though.)<br></div><div> <br></div></div>Albert<br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Dr. Albert Gr"af<br>Computer Music Research Group, JGU Mainz, Germany<br>Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a><br>WWW: <a href="https://plus.google.com/+AlbertGraef" target="_blank">https://plus.google.com/+AlbertGraef</a></div></div>
</div></div>