This is probably unrelated but worth trying:
When you get "broken pipe" did it worked in the first place?. i.e it was
running and you got the error or you get the error as son as you start it?
If you got it as soon as started it could "probably" be that there's
"white space" somewhere in
:) I do work on windows, but this issue happens only with macOs (which I
don't have at home, and maybe now and then would be able to get access to).
I can try to have a look, next time I'm near a mac computer.
As my past experience following build instructions is close to 90%
unsuccess rate -
D'oh. I don't know why I though Joao was on Windows... Thanks for the
correction!
Note that lldb is the clang debugger and it works slightly different
than GDB. But you can do the same things.
On 17.11.2021 15:07, Lucas Cordiviola wrote:
@Christof,
I think Joao is needing the *macOS*
@Christof,
I think Joao is needing the *macOS* pdmax.
@Joao,
Everything that Christof said applies if you follow the macOS part:
https://github.com/pure-data/pure-data/blob/master/INSTALL.txt
you just need to install xcode with this command on a terminal:
xcode-select --install
macOS
You would have to build the pdmax external from source with debug
symbols to get meaningful information in the debugger. This means you
would need to setup Msys2, as described in the "Windows" section in
https://github.com/pure-data/pure-data/blob/master/INSTALL.txt.
Actually, if the aim is
is that something a "normal user" like me (someone that only uses the
surface of the software) can do, or it has to do with C or any other
custom compiled/prepared versions?
On Wed, 17 Nov 2021 at 01:06, Christof Ressi wrote:
> You can attach GDB to a running or even a not-yet-running
It's still 0.51-4 being used. But the strange part is that it works in
one version and it doesn't in the other. I think I remember also working
completely in an older system, but now I would need to have access to it
again.
If by any chance you're using pd 0.52 (test version) then I think
You can attach GDB to a running or even a not-yet-running application.
When that application crashes, you get a backtrace. That's how I found
the crash in the [pd~] subprocess.
Personally, I use Qt Creator because it has a nice graphical front-end
for GDB where I can easily step through
If by any chance you're using pd 0.52 (test version) then I think
it can crash when used as a subprocess (this should be fixed for the next
test release). If you're using Pd 0.51-4 the problem is something else.
The "broken pipe" message means the subprocess died suddenly for some reason.
But I
Hello list,
I have a max patch with pd inside through the pd~ object. But I'm
getting the "broken pipe" error in some cases in a mac, such as:
- in a compiled standalone it usually works
- in the original patch it doesn't
- both patches were made in the same system, with the latest pdmax
10 matches
Mail list logo
