Hi guys,
I'm writing a Pd external, but when I turn on the DSP Pd crashes. Obviously the problem is in my perform routine, and looking at Console (a log viewer on Mac OS X) I can confirm it. So I would like to know if someone of you is using a debugger program in order to fix the problem. I try lldb on Mac Terminal but without result; I saw some time ago that Puckette quotes Valgrind[1], but probably in a different contest. Is it a solution?
Thank you in advance for your help. Best regards, Marco
[1]: mail "problems with pd-0.46-6 and jack" on April 30.
gdb
On Thu, Jun 11, 2015 at 9:22 PM, Marco Matteo Markidis < mm.markidis@gmail.com> wrote:
Hi guys,
I'm writing a Pd external, but when I turn on the DSP Pd crashes. Obviously the problem is in my perform routine, and looking at Console (a log viewer on Mac OS X) I can confirm it. So I would like to know if someone of you is using a debugger program in order to fix the problem. I try lldb on Mac Terminal but without result; I saw some time ago that Puckette quotes Valgrind[1], but probably in a different contest. Is it a solution?
Thank you in advance for your help. Best regards, Marco
[1]: mail "problems with pd-0.46-6 and jack" on April 30.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
As I know, gdb is no more present in Mac. I think it was substituted by lldb. Anyway, on gdb what is the correct syntax in order to launch your external?
Thank you,
Marco
2015-06-11 14:39 GMT+02:00 i go bananas hard.off@gmail.com:
gdb
On Thu, Jun 11, 2015 at 9:22 PM, Marco Matteo Markidis < mm.markidis@gmail.com> wrote:
Hi guys,
I'm writing a Pd external, but when I turn on the DSP Pd crashes. Obviously the problem is in my perform routine, and looking at Console (a log viewer on Mac OS X) I can confirm it. So I would like to know if someone of you is using a debugger program in order to fix the problem. I try lldb on Mac Terminal but without result; I saw some time ago that Puckette quotes Valgrind[1], but probably in a different contest. Is it a solution?
Thank you in advance for your help. Best regards, Marco
[1]: mail "problems with pd-0.46-6 and jack" on April 30.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 2015-06-11 14:42, Marco Matteo Markidis wrote:
As I know, gdb is no more present in Mac. I think it was substituted by lldb. Anyway, on gdb what is the correct syntax in order to launch your external?
you cannot "launch" an external. anyhow:
on linu x i use: $ gdb --args pd -stderr -nrt -nosound -lib /path/to/external test.pd (gdb) run [...run-until-crash...] (gdb) bt
on OSX you need to specify the full path to the actual Pd-binary . the important Pd-flags are: "-nrt" (if you don't want to clutter your gdb console with "pd-watchdog: signalling...") and "-stderr" (in case you print something important before the crash)
fgmasdr IOhannes
PS: btw, check your args and the return value (or rather: whether the offset of the t_int* is correct) in the perform routine.
Dear Iohannes,
thank you. On Mac I do: $ lldb -- /Applications/Pd.app/Contents/MacOS/Pd -stderr -nrt -nosound -lib vpdelay~-help.pd $ (lldb) target create "/Applications/Pd.app/Contents/MacOS/Pd" $ Segmentation fault: 11 without making the run command. I tried even with other Pd stuff and I always get this problem. From Console I see that it's an EXC_BAD_ACCESS (SIGSEGV). I am using the latest version of Pd Vanilla (0.46.6) for Mac 64 bit on Mac Yosemite.
Best regards, Marco
2015-06-11 17:17 GMT+02:00 IOhannes m zmoelnig zmoelnig@iem.at:
On 2015-06-11 14:42, Marco Matteo Markidis wrote:
As I know, gdb is no more present in Mac. I think it was substituted by lldb. Anyway, on gdb what is the correct syntax in order to launch your
external?
you cannot "launch" an external. anyhow:
on linu x i use: $ gdb --args pd -stderr -nrt -nosound -lib /path/to/external test.pd (gdb) run [...run-until-crash...] (gdb) bt
on OSX you need to specify the full path to the actual Pd-binary . the important Pd-flags are: "-nrt" (if you don't want to clutter your gdb console with "pd-watchdog: signalling...") and "-stderr" (in case you print something important before the crash)
fgmasdr IOhannes
PS: btw, check your args and the return value (or rather: whether the offset of the t_int* is correct) in the perform routine.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hey Marco,
If you have Xcode installed try the following:
Build the external
Launch Pd
In Xcode: Debug > Attach to process > Pd (pid) (not pd with icon but pd
in the latter half of list, Pd runtime)
- Open Patch that contains your freshly built external
Cheers,
Joe
On 11 June 2015 at 16:47, Marco Matteo Markidis mm.markidis@gmail.com wrote:
Dear Iohannes,
thank you. On Mac I do: $ lldb -- /Applications/Pd.app/Contents/MacOS/Pd -stderr -nrt -nosound -lib vpdelay~-help.pd $ (lldb) target create "/Applications/Pd.app/Contents/MacOS/Pd" $ Segmentation fault: 11 without making the run command. I tried even with other Pd stuff and I always get this problem. From Console I see that it's an EXC_BAD_ACCESS (SIGSEGV). I am using the latest version of Pd Vanilla (0.46.6) for Mac 64 bit on Mac Yosemite.
Best regards, Marco
2015-06-11 17:17 GMT+02:00 IOhannes m zmoelnig zmoelnig@iem.at:
On 2015-06-11 14:42, Marco Matteo Markidis wrote:
As I know, gdb is no more present in Mac. I think it was substituted by lldb. Anyway, on gdb what is the correct syntax in order to launch your
external?
you cannot "launch" an external. anyhow:
on linu x i use: $ gdb --args pd -stderr -nrt -nosound -lib /path/to/external test.pd (gdb) run [...run-until-crash...] (gdb) bt
on OSX you need to specify the full path to the actual Pd-binary . the important Pd-flags are: "-nrt" (if you don't want to clutter your gdb console with "pd-watchdog: signalling...") and "-stderr" (in case you print something important before the crash)
fgmasdr IOhannes
PS: btw, check your args and the return value (or rather: whether the offset of the t_int* is correct) in the perform routine.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hi Joe,
thank you so much! I really appreciate your method. Thank you again.
Best regards, Marco
2015-06-11 17:54 GMT+02:00 Joe White white.joe4@gmail.com:
Hey Marco,
If you have Xcode installed try the following:
Build the external
Launch Pd
In Xcode: Debug > Attach to process > Pd (pid) (not pd with icon but pd
in the latter half of list, Pd runtime)
- Open Patch that contains your freshly built external
Cheers,
Joe
On 11 June 2015 at 16:47, Marco Matteo Markidis mm.markidis@gmail.com wrote:
Dear Iohannes,
thank you. On Mac I do: $ lldb -- /Applications/Pd.app/Contents/MacOS/Pd -stderr -nrt -nosound -lib vpdelay~-help.pd $ (lldb) target create "/Applications/Pd.app/Contents/MacOS/Pd" $ Segmentation fault: 11 without making the run command. I tried even with other Pd stuff and I always get this problem. From Console I see that it's an EXC_BAD_ACCESS (SIGSEGV). I am using the latest version of Pd Vanilla (0.46.6) for Mac 64 bit on Mac Yosemite.
Best regards, Marco
2015-06-11 17:17 GMT+02:00 IOhannes m zmoelnig zmoelnig@iem.at:
On 2015-06-11 14:42, Marco Matteo Markidis wrote:
As I know, gdb is no more present in Mac. I think it was substituted by lldb. Anyway, on gdb what is the correct syntax in order to launch your
external?
you cannot "launch" an external. anyhow:
on linu x i use: $ gdb --args pd -stderr -nrt -nosound -lib /path/to/external test.pd (gdb) run [...run-until-crash...] (gdb) bt
on OSX you need to specify the full path to the actual Pd-binary . the important Pd-flags are: "-nrt" (if you don't want to clutter your gdb console with "pd-watchdog: signalling...") and "-stderr" (in case you print something important before the crash)
fgmasdr IOhannes
PS: btw, check your args and the return value (or rather: whether the offset of the t_int* is correct) in the perform routine.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
i go bananas -
IOhannes m zmoelnig -
Joe White -
Marco Matteo Markidis