[Done] Set JSC_SIGNAL_FOR_GC ...

[useful]

SB310B1 Ubuntu24.04XFCE ( https://sourceforge.net/projects/runtu/ ... 4.04/XFCE/ )

"Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal"

Message at startup. I'm not sure if this is an error, but if it's possible to fix the cause of the message, I'd like to know how.
p.s.
at first glance, this does not interfere with the work.
p.p.s.
JSC_SIGNAL_FOR_GC is a variable that specifies which signal should be used for garbage collection (GC) in the WebKit library. The SIGUSR1 signal is used by default.

If the application has its own SIGUSR1 signal handler installed, ASC_SIGNAL_FOR_GC allows you to configure a different signal for WebKit. This can be useful, for example, when inserting the JavaScriptCore library into a Linux application where there is a problem with SIGUSR1 signal processing.

[Fred]

We don't use this so I don't think it's a SB issue.

[useful]

Nevertheless, I checked on classic UBUNTU 24.04 in live mode. When starting SpiderBasic ide, I get the same message.
p.s.
Is there no such message in the distribution on which you are developing and testing? Maybe something needs to be added to the configuration? Or do you see the same thing in yourself that I do?

[Fred]

My bad, actually we use this for the thread library, so I added the env var to change the default signal to SIGUSR2. Why GTK Webkit doesn't do that automatically is a bit a mystery to me.

[useful]

My bad, actually we use this for the thread library, so I added the env var to change the default signal to SIGUSR2. Why GTK Webkit doesn't do that automatically is a bit a mystery to me.

Can you give us instructions? I still see this message in the new beta version.

[Fred]

Which Linux version do you use ? 20.04 or 24.04 ?

[useful]

SB for U24.04 (SpiderBasic_Linux3_x64_beta_3.10 ...)

Ubuntu24.04XFCE ( https://sourceforge.net/projects/runtu/ ... 4.04/XFCE/ )
and
WSL UBUNTU 24.04.

I haven't checked on classic UBUNTU 24.04 yet.

p.s. checked it out:
ubuntu@ubuntu:~/Sys/spiderbasic$ ./launch.sh
Overriding existing handler For signal 10. Set JSC_SIGNAL_FOR_GC If you want WebKit To use a different signal

p.p.s. I'm sometimes a pathological perfectionist, but if you can figure it out, it's better to figure it out.

[Fred]

could you try to set:

export JSC_SIGNAL_FOR_GC=12

before launching the IDE to see if it changes something ?

[useful]

WSL2 UBUNTU 24.04
-----------------
PowerShell 7.5.2
PS C:\Users\kiv> wsl mc

kiv@JUNIBOX:/mnt/c/Work/testwsl/spiderbasic$ export JSC_SIGNAL_FOR_GC=12
kiv@JUNIBOX:/mnt/c/Work/testwsl/spiderbasic$ ./launch.sh
ERROR: invalid option: JSC_SIGNAL_FOR_GC=12
ERROR: invalid option: JSC_SIGNAL_FOR_GC=12
==========
RuntuXFCE
----------
kiv@RX24:~/Sys/spiderbasic$ export JSC_SIGNAL_FOR_GC=12
kiv@RX24:~/Sys/spiderbasic$ ./launch.sh
Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal
ERROR: invalid option: JSC_SIGNAL_FOR_GC=SIGUSR2
ERROR: invalid option: JSC_SIGNAL_FOR_GC=SIGUSR2

p.s. But, at first glance, this does not interfere with the work.

[Fred]

Yes, that's weird. I will change the PB internal one then and it should fix it.