[ISSUE] All PHP versions with imagick enabled (`extension=imagick`) segfault

[ISSUE] All PHP versions with imagick enabled (`extension=imagick`) segfault

[TinfoilSubmarine]

[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]

New issue by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/issues/48500

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.11_1 x86_64 AuthenticAMD uptodate rrmFFFFFFFFFFFFFFFFFFF

### Package(s) Affected

php8.1-imagick-3.7.0_9, php8.2-imagick-3.7.0_9, php8.3-imagick-3.7.0_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/Imagick/imagick/issues/609
https://github.com/Imagick/imagick/issues/636

### Expected behaviour

Using the PHP executable should suceed.

### Actual behaviour

Segfaults immediately no matter what:
```
$ php -a                                                                                             
zsh: segmentation fault  php -a
$ php                                                                                            
zsh: segmentation fault  php
$ php --version                                                                                  
zsh: segmentation fault  php --version                                                                                       
```

### Steps to reproduce

1. Install any php version available in void-packages as well as the relevant imagick (e.g. `xi php8.3-imagick`).
2. Enable imagick in php.ini: `extension=imagick`.
3. Run the `php` executable with any arguments.

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[TinfoilSubmarine]

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

New comment by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1924754633

Comment:
As mentioned in [this thread](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109634#c4), these are some options:

> libgomp can be only dlopened in threaded apps if there is still space in the static TLS surplus, which unfortunately some versions of glibc use even for normal TLS rather than just static TLS.
> So, LD_PRELOAD=libgomp.so.1, or link the program with libgomp.so.1 rather than just its libraries, or dlopen it before spawning threads.
> This is how glibc behaves, and unless we want to slow down libgomp extremely, there is nothing that can be done about it on the GCC side.

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[TinfoilSubmarine]

[-- Attachment #1: Type: text/plain, Size: 243 bytes --]

New comment by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1924757303

Comment:
I also should note that this only started occurring with the update to `libgomp-13.2.0_1`.

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 194 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1924773487

Comment:
maybe it needs a rebuild for the new libgomp?

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[TinfoilSubmarine]

[-- Attachment #1: Type: text/plain, Size: 166 bytes --]

New comment by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1924781100

Comment:
Already tried

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[sgn]

[-- Attachment #1: Type: text/plain, Size: 175 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925024082

Comment:
We may link php to libgomp instead?

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 435 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925092227

Comment:
The crash occurs in `initialize_env()`  on the following line: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/libgomp/env.c#L2062

Importing 15345980633c502f0486a2e40e96224f49134130 in to libgomp does appear to fix the issue for me (adds an if statement before de-referencing).

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 531 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925092227

Comment:
The crash occurs in `initialize_env()`  on the following line: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/libgomp/env.c#L2062

Applying the following patch does appear to fix the issue for me https://github.com/gcc-mirror/gcc/commit/15345980633c502f0486a2e40e96224f49134130 in to libgomp does appear to fix the issue for me (adds an if statement before de-referencing).

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 541 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925092227

Comment:
The crash occurs in `initialize_env()`  on the following line: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/libgomp/env.c#L2062

Applying the following patch does appear to fix the issue for me https://github.com/gcc-mirror/gcc/commit/15345980633c502f0486a2e40e96224f49134130 in to libgomp does appear to fix the issue for me (adds an if statement before de-referencing `environ`).

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925092227

Comment:
The crash occurs in `initialize_env()`  on the following line: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/libgomp/env.c#L2062

Applying the following patch does appear to fix the issue for me https://github.com/gcc-mirror/gcc/commit/15345980633c502f0486a2e40e96224f49134130 in to libgomp does appear to fix the issue for me (adds an if statement before de-referencing `environ`).

It seems like fedora backported this patch to their branch (hence why no issues there).

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 525 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925092227

Comment:
The crash occurs in `initialize_env()`  on the following line: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/libgomp/env.c#L2062

Applying the following patch does appear to fix the issue for me https://github.com/gcc-mirror/gcc/commit/15345980633c502f0486a2e40e96224f49134130.
It seems like fedora backported this patch to their branch (hence why no issues there).

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 527 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925092227

Comment:
The crash occurs in `initialize_env()`  on the following line: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/libgomp/env.c#L2062

Applying the following patch does appear to fix the issue for me https://github.com/gcc-mirror/gcc/commit/15345980633c502f0486a2e40e96224f49134130.

It seems like fedora backported this patch to their branch (hence why no issues there).

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 531 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925092227

Comment:
The crash occurs in `initialize_env()`  on the following line: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/libgomp/env.c#L2062

Applying the following patch does appear to fix the issue for me https://github.com/gcc-mirror/gcc/commit/15345980633c502f0486a2e40e96224f49134130.

It seems like fedora backported this patch to their gcc branch (hence why no issues there).

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925092227

Comment:
The crash occurs in `initialize_env()`  on the following line: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/libgomp/env.c#L2062

Applying the following patch does appear to fix the issue for me https://github.com/gcc-mirror/gcc/commit/15345980633c502f0486a2e40e96224f49134130.

This patch was also backported to the gcc-13 branch: https://github.com/gcc-mirror/gcc/commits/releases/gcc-13/libgomp/env.c

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 606 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925092227

Comment:
The crash occurs in `initialize_env()`  on the following line: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/libgomp/env.c#L2062

Applying the following patch does appear to fix the issue for me https://github.com/gcc-mirror/gcc/commit/15345980633c502f0486a2e40e96224f49134130.

This patch was also backported to the gcc-13 branch: https://github.com/gcc-mirror/gcc/commits/releases/gcc-13/libgomp/env.c (and is also in Fedora's gcc 13.2 branch)

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[oreo639]

[-- Attachment #1: Type: text/plain, Size: 248 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925216346

Comment:
@TinfoilSubmarine When you are avaliable, can you update and verify that libgomp-13.2.0_2 works for you?

Re: [ISSUE] [CLOSED] All PHP versions with imagick enabled (`extension=imagick`) segfault

[TinfoilSubmarine]

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

Closed issue by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/issues/48500

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.11_1 x86_64 AuthenticAMD uptodate rrmFFFFFFFFFFFFFFFFFFF

### Package(s) Affected

php8.1-imagick-3.7.0_9, php8.2-imagick-3.7.0_9, php8.3-imagick-3.7.0_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/Imagick/imagick/issues/609
https://github.com/Imagick/imagick/issues/636

### Expected behaviour

Using the PHP executable should suceed.

### Actual behaviour

Segfaults immediately no matter what:
```
$ php -a                                                                                             
zsh: segmentation fault  php -a
$ php                                                                                            
zsh: segmentation fault  php
$ php --version                                                                                  
zsh: segmentation fault  php --version                                                                                       
```

### Steps to reproduce

1. Install any php version available in void-packages as well as the relevant imagick (e.g. `xi php8.3-imagick`).
2. Enable imagick in php.ini: `extension=imagick`.
3. Run the `php` executable with any arguments.

Re: All PHP versions with imagick enabled (`extension=imagick`) segfault

[TinfoilSubmarine]

[-- Attachment #1: Type: text/plain, Size: 170 bytes --]

New comment by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1925891536

Comment:
Yep, fixed for me