[L2Ork-dev] Potential Gem bug?

IOhannes m zmoelnig zmoelnig at iem.at
Tue Apr 23 05:35:14 EDT 2019


On 14.04.19 17:48, Ivica Ico Bukvic wrote:
> IOhannes et al.,

i'm just back from easter hols. sorry for the delay.

> I just checked out the latest Gem (0.94 branch) by doing:
> git clone https://git.code.sf.net/p/pd-gem/gem pd-gem-gem
> When starting pd-l2ork, it segfaults with the following backtrace. Any idea
> what may be wrong? Is this a stable branch?

yes, it's a stable release.

however, Gem does some magic to add it's own path to the search-paths of
Pd (if it is not already added), and while doing so it might hit a
binary incompatibility between purr-data and Pd.

Gem will use the safer "add-to-path" message to "pd", if it detects a
compatible version of Pd (comparing the output of sys_getversion()
against (0,47)). this seems to fail with purr-data, so it falls back to
calling "namelist_append" to append the path to the "sys_searchpath"

probably jonathan can shed some light why this crashes.

> [submodule "Gem"]
> path = Gem
> url = git://git.code.sf.net/p/pd-gem/gem

i'd suggest using https://git.iem.at/pd/Gem as upstream (or
i still mirror to sourceforge for legacy reasons, but who knows...


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20190423/00550143/attachment.sig>

More information about the L2Ork-dev mailing list