On 11/07/2023 07:01, Linux ROUEN Normandie wrote:
- Debugger back-trace
(https://nc.nubegris.com.ar/index.php/s/JwEjrPDEyP53oL7) The described steps seem to be for Arch Linux or fork distributions and not for Windows?
It's for Windows. MSYS2 brings a lot of "ported-for-Windows" Linux commands: from https://www.msys2.org/wiki/MSYS2-introduction/
"MSYS2 uses a port of*pacman*(known from Arch Linux) for package management"
- Link to get Pd-0.54-0 with debug symbols
(https://nc.nubegris.com.ar/index.php/s/eKrTbHE4iyqAgAg) Opening this pd-0.54.0-debug.zip (10.5 MB) file looks like for Windows. But, for example, its Tcl/Tk and Wish files versions are '85' when in the portable version of Pd 0.54.0 they are in '86' version? So at least for them we will not compare apples with apples!
Wish85 and Tk85 are just the GUI portion that Pd make use of. When you build Pd for Windows (https://puredata.info/docs/developer/WindowsMinGW) these 2 apps are extracted from https://github.com/pure-data/pure-data/blob/master/msw/pdprototype.tgz and placed in the built app. this is useful for us so that we can easily test our compiled Pd. On Miller's builds he places a newer versions of tcl/tk . Also interesting is that the 85 versions from pdprototype.tgz are 32-bit apps (we needed them like that also to test on older 32-bit only Windows (as many XP machines). But since Pd and the GUI talk via a loopback local network connection the thing works anyway,
- Any other things you can think about for helping a new player in the
Debug area...
I also want to contribute solving this mystery! 😉
Mensaje telepatico asistido por maquinas.