Selecting any object and pasting bogus stuff (e.g. random text) crashes Purr-Data
Tested on Windows 2.11, likely affects all platforms.
Activity
added critical label
gdb backtrace:
Thread 1 received signal SIGSEGV, Segmentation fault. 0x675a2277 in pd!canvas_done_popup () from C:\Program Files (x86)\Purr Data\bin\pd.dll (gdb) back #0 0x675a2277 in pd!canvas_done_popup () from C:\Program Files (x86)\Purr Data\bin\pd.dll #1 (closed) 0x675bdbc4 in pd_typedmess () from C:\Program Files (x86)\Purr Data\bin\pd.dll #2 (closed) 0x675bd703 in pd_typedmess () from C:\Program Files (x86)\Purr Data\bin\pd.dll #3 (closed) 0x675c7147 in pd!binbuf_eval () from C:\Program Files (x86)\Purr Data\bin\pd.dll #4 (closed) 0x675cf886 in socketreceiver_read () from C:\Program Files (x86)\Purr Data\bin\pd.dll #5 (closed) 0x675cee60 in sys_getblksize () from C:\Program Files (x86)\Purr Data\bin\pd.dll #6 (closed) 0x675cb59a in pd!m_mainloop () from C:\Program Files (x86)\Purr Data\bin\pd.dll #7 (closed) 0x675cea98 in sys_main () from C:\Program Files (x86)\Purr Data\bin\pd.dll #8 0x00402730 in ?? () #9 (closed) 0x00401386 in ?? () #10 (closed) 0x75836359 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll #11 (closed) 0x777a7c24 in ntdll!RtlGetAppContainerNamedObjectPath () from C:\WINDOWS\SYSTEM32\ntdll.dll #12 (closed) 0x777a7bf4 in ntdll!RtlGetAppContainerNamedObjectPath () from C:\WINDOWS\SYSTEM32\ntdll.dll #13 (closed) 0x00000000 in ?? ()
Looks like this may be a side-effect of allowing pasting patch code (not sure if this is the leftover from 1.x or the last year's GSoC)
Further testing reveals that Purr-Data has additional regression when compared to the 1.x branch. Selecting text from a saved patch and pasting it into a new patch should alter it and populate it accordingly. It doesn't even though it acknowledges attempted paste by making the patch dirty. Attempting to paste while having an object selected should try to autopatch and this crashes Purr-Data.
It looks that my previously reported paste crash where you copy bogus text and then select and object in edit mode and click paste, then crash with a segfault, is also the case with the paste from clipboard, regardless whether the text is bogus or not.
The only time it does not crash is if you use text/bogus text without anything selected inside the canvas and then do regular paste in which case the only thing you get is canvas dirty signal.
backtrace:
0x6754217a in pd!canvas_declare () from C:\Program Files (x86)\Purr Data\bin\pd.dll (gdb) back #0 0x6754217a in pd!canvas_declare () from C:\Program Files (x86)\Purr Data\bin\pd.dll #1 (closed) 0x675bdf8a in pd_typedmess () from C:\Program Files (x86)\Purr Data\bin\pd.dll #2 (closed) 0x675bda73 in pd_typedmess () from C:\Program Files (x86)\Purr Data\bin\pd.dll #3 (closed) 0x675c74b7 in pd!binbuf_eval () from C:\Program Files (x86)\Purr Data\bin\pd.dll #4 (closed) 0x675cfbf6 in socketreceiver_read () from C:\Program Files (x86)\Purr Data\bin\pd.dll #5 (closed) 0x675cf1d0 in sys_getblksize () from C:\Program Files (x86)\Purr Data\bin\pd.dll #6 (closed) 0x675d183d in sys_pollgui () from C:\Program Files (x86)\Purr Data\bin\pd.dll #7 (closed) 0x675cb62b in pd!m_mainloop ()
This one is fixed by the !379 (closed)
