Menu
▾
▴
#132 reload plugin results in
Just tried GXSM2-1.24.0 with Open Source SPM Controller (Code 20.14) on Ubuntu 10.04.
If you try a reload plugins GXSM will stop as a segmentation fault occurs. Here is the output of the terminal after starting gxsm2 --debug-level=5 --pi-debug-level=5 > error
(gxsm_main.C: main) Gxsm-DEBUG-MESSAGE :
- Setup dynamic preferences
(gxsm_main.C: main) Gxsm-DEBUG-MESSAGE :
- GXSM run druids check
(gxsm_conf.C: GetStr) Gxsm-DEBUG-MESSAGE :
- XsmRM::get-string*: /apps/gxsm2/GUI-global/System/First-Start-Key = key default: Segmentation fault
The error file contains the following lines after gxsm2 was started successfully:
SR-MK2_HwI::sranger_mk2_hwi_cleanup -- Plugin Cleanup, --Menu
SR-MK2-HwI::sranger_mk2_hwi_cleanup -- Plugin Cleanup --DSPCoCl
SR-MK2_HwI::sranger_mk2_hwi_cleanup -- Plugin Cleanup --sr_hwi
SR-MK2-HwI::sranger_mk2_hwi_cleanup -- Plugin Cleanup --Info
SR-MK2-HwI::sranger_mk2_hwi_cleanup -- Plugin Cleanup done.
SR-MK2-HwI::sranger_mk2_hwi_query:: <SRangerMK2:SPM>
SR-MK2-HwI::sranger_mk2_hwi_query:: ConnectPluginToCDFSaveEvent
loaded HwI PI (OK) :: sranger_mk2_hwi-HW-INT-1S-SHORT
Thorsten :-)
Sorry -- PlugIn reload can not be used if a HwI (Hardware) is hooked up -- this HwI plugin can not be reloaded on the fly per design and it will cause a problem. (I may disable this function in future with active HwI)
This is function was designed for on-the-fly math plugin testing and development purposes...
PLEASE DO NOT USE WHILE NORMAL OPERATION WITH HARDWARE.
Just testing on the "Lancaster Classics" - while shutting down I get the following message:
....
SR-MK2/3_HwI::sranger_mk2_hwi_cleanup -- Plugin Cleanup, --Menu
SR-MK2/3_HwI::sranger_mk2_hwi_cleanup -- Plugin Cleanup --DSPCoCl
Notebook DSPControl tab removed: window=1 tab=0 page=0
Notebook DSPControl tab removed: window=1 tab=2 page=0
Notebook DSPControl tab removed: window=1 tab=3 page=0
Notebook DSPControl tab removed: window=1 tab=13 page=0
Segmentation fault
The segmentation fault is surely while shutting down the hwi (sranger_mk2). As a consequence the settings in the mover window are not saved. I guess it is just an issue about the sequence of unloading. So the general DSPControl window is unloaded before the DSPMover window. As the first crashed the second never gets the callback to save the data which is actually done in the respective destructor.
I will try to save the parameter in the DSPupdate call of the DSPMover-object.
Thorsten :-)
Please never do a plugin reload with a HwI plugin loaded (hardware attached) -- per design will not work as the HwI links in at an very early stage and can NOT on the fly be reloaded -- and sorry, yes, it's not prohibited.
Well, I could eliminate the option... it's only supposed to be use in analysis mode (-h no) and for math plugin developments very handy.
I had a look -- there is actually code to manage the HwI reload in the gxsm core (works with the "dummy" HwI), but I remember some issue eventually with references to it pending via the "registration mechanism" and it's hard to fix w/o loosing some functionality. In general HwI's can be re loadable, but it depends on the HwI design itself, in this case (SRanger*) it's not working OK. I apologize.
It is not so much about reloading the plugins but closing the program and have the parameters saved which are displayed in the windows of the plugins. That is why I re-opened this thread again. There is alway a segmentation fault when shutting down gxsm2. You usually see that only if you start gxsm in the terminal. The segmentation fault happens before all parameters of the HWI are saved.
Absolutely NO plugin reloading with active HwI. (Need to prevent in future)