On 12/11/2019 2:36 PM, IOhannes m zmölnig wrote:
> the proper condition is:
> if(pddplink_class) {
>dirsym=...
> } else {
>dirsym=NULL;
> }
Ok right, I posted what i did because I was not sure. Had fixed it :)
Coming back to the subject of this thread:
The combined single/double dll is
Am 11. Dezember 2019 17:32:40 MEZ schrieb Lucas Cordiviola
>
> if (dirsym) {
> dirsym = pddplink_class->c_externdir; /* FIXME */
> sys_vgui("source {%s/pddplink.tcl}\n", dirsym->s_name);
> } else {
> dirsym = NULL;
> }
this is bogus.
you set dirsym to NULL if it's
Thanks Christof now everything's fine and I learned how to use msys2 gdb
compiling with "alldebug" with pd-lib-builder.
As for the "null pointer check" I just did this on pddplink_setup():
~
if (dirsym) {
dirsym = pddplink_class->c_externdir; /* FIXME */
t; Von: "Lucas Cordiviola"
> An: "pd-dev@lists.iem.at"
> Betreff: Re: [PD-dev] Double precision externals extensions.
>
> I could get this from linux, at least is something:
>
> ~
>
> Program received signal SIGSEGV, Segmentation fault.
>
> 0x
I could get this from linux, at least is something:
~
Program received signal SIGSEGV, Segmentation fault.
0x76170e93 in pddplink_setup () at pddp/pddplink.c:353
353 sys_vgui("source {%s/pddplink.tcl}\n", dirsym->s_name);
~~~
But no worries is just an edge
em.at" , "Christof Ressi"
>
> Betreff: Re: [PD-dev] Double precision externals extensions.
>
> This is the backtrace with Msys2:
>
> ~~
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x6eb469f5 in pddplink_setup (
>>
>> Christof
>>
>>> Gesendet: Dienstag, 10. Dezember 2019 um 22:59 Uhr
>>> Von: "Lucas Cordiviola"
>>> An: "pd-dev@lists.iem.at" , "Christof Ressi"
>>>
>>> Betreff: Re: [PD-dev] Double precision externals extensio
; run // actually run the program
> ... wait for crash ...
>> bt // get the backtrace
> press Enter repeatedly to see more lines
>
> Christof
>
>> Gesendet: Dienstag, 10. Dezember 2019 um 22:59 Uhr
>> Von: "Lucas Cordiviola"
>> An: "pd-dev@lists.iem.at&
10. Dezember 2019 um 23:37 Uhr
*Von:* "Lucas Cordiviola" <mailto:lucard...@hotmail.com>
*An:* "pd-dev@lists.iem.at"<mailto:pd-dev@lists.iem.at>
<mailto:pd-dev@lists.iem.at>
*Betreff:* Re: [PD-dev] Double precision externals extensions.
Is this: "A_FLOAT&quo
I get the segfault on linux (it also crashes Pd-double)
~~~
Program received signal SIGSEGV, Segmentation fault.
0x76170e93 in pddplink_setup ()
from
/home/lucarda/Desktop/luclibdep/00-lucarda-external-dep/out64single/lucdep/liblucdep.so
~~~
:)
Mensaje
> Gesendet: Dienstag, 10. Dezember 2019 um 22:59 Uhr
> Von: "Lucas Cordiviola"
> An: "pd-dev@lists.iem.at" , "Christof Ressi"
>
> Betreff: Re: [PD-dev] Double precision externals extensions.
>
> @christof
>
> How do I build Pd with
uested.
Just some brainstorming.
Christof
> Gesendet: Dienstag, 10. Dezember 2019 um 23:06 Uhr
> Von: "IOhannes m zmölnig"
> An: pd-dev@lists.iem.at
> Betreff: Re: [PD-dev] Double precision externals extensions.
>
> On 12/10/19 10:48 PM, Christof Ressi wrote:
> >
>
n atom type, so
> it's 100% unrelated to single/double precision.
> *Gesendet:* Dienstag, 10. Dezember 2019 um 23:37 Uhr
> *Von:* "Lucas Cordiviola"
> *An:* "pd-dev@lists.iem.at"
> *Betreff:* Re: [PD-dev] Double precision externals extensions.
> Is this: "A_FLOAT" forbidden?
I'm not sure what you mean exactly, but A_FLOAT is an atom type, so it's 100% unrelated to single/double precision.
Gesendet: Dienstag, 10. Dezember 2019 um 23:37 Uhr
Von: "Lucas Cordiviola"
An: "pd-dev@lists.iem.at"
Betre
Is this: "A_FLOAT" forbidden?
~
void pddplink_setup(void)
{
t_symbol *dirsym;
pddplink_class = class_new(gensym("pddplink"),
(t_newmethod)pddplink_new,
(t_method)pddplink_free,
sizeof(t_pddplink),
CLASS_NOINLET | CLASS_PATCHABLE,
A_GIMME, 0);
class_addanything(pddplink_class,
On 12/10/2019 6:32 PM, IOhannes m zmölnig wrote:
> On 12/10/19 9:45 PM, Lucas Cordiviola wrote:
>> But I'm creating a single binary external with a collection of authors
>> [zexy] [cyclone] [ggee] [pddplink] ...
> what's the purpose of this?
> and what's the license?
Currently I share Pd-Albums
.
>
> Is there an easier way?
>
> If not, then a new extension could be handy, so people can throw both
> versions into the same folder.
>
> Christof
>
>> Gesendet: Dienstag, 10. Dezember 2019 um 21:45 Uhr
>> Von: "Lucas Cordiviola"
>> An:
On 12/10/19 10:48 PM, Christof Ressi wrote:
>
> I'm also interested in how this works. The following solution popped up in my
> head: compile the object twice, one time with -DPD_FLOATSIZE=32 and another
> time with -DPD_FLOATSIZE=64, with different setup functions based on
> -DPD_FLOATSIZE,
up functions).
Is there an easier way?
If not, then a new extension could be handy, so people can throw both versions
into the same folder.
Christof
> Gesendet: Dienstag, 10. Dezember 2019 um 21:45 Uhr
> Von: "Lucas Cordiviola"
> An: "pd-dev@lists.iem.at"
> Betreff: Re:
On 12/10/19 9:45 PM, Lucas Cordiviola wrote:
> But I'm creating a single binary external with a collection of authors
> [zexy] [cyclone] [ggee] [pddplink] ...
what's the purpose of this?
and what's the license?
>
> I create a setup for the lib and is working *OK* in Pd-w64-32 but it
> crashed
On 12/10/2019 4:54 PM, IOhannes m zmölnig wrote:
> # avoiding crashes
> an external that has been compiled with single-precision will not
> register objectclasses in a double-precision Pd - so the doubl-precision
> Pd will not know about those new objects and not crash while using them.
> same
On 12/10/19 7:22 PM, Lucas Cordiviola wrote:
> Could we have special extension for double-precision external?
>
> Something like foo.m_amd64dp ?
>
> This way we can have external pkgs including both single and double
> externals.
>
> Also instruct Pd to *not* try to load the not current
Could we have special extension for double-precision external?
Something like foo.m_amd64dp ?
This way we can have external pkgs including both single and double
externals.
Also instruct Pd to *not* try to load the not current precision and
avoid crashes.
--
Mensaje telepatico asistido
23 matches
Mail list logo
