Hi! Thank you for the information about other related problem (I mean #1073346).
> I find surprising that you always get the infinite recursion problem.
Before your message I had one failed build with infinite recursion
problem in recent Debian Trixie i386 and one failed build with
infinite recur
> This is something somewhat similar to https://bugs.debian.org/922075#20
Jérémy, thank you for the link!
I'll try to read that thread later. It will take some time.
And now just for info I want to share detailed backtrace with pointers
to sources at all frames of backtrace (not only in nodejs bu
I built source package nodejs_18.19.0+dfsg-6~deb12u2 in Debian
Bookworm i386 and installed result deb packages into system.
Packages with dbgsym were also installed.
Then I tried to reproduce segfault with simple way explained earlier
and now I see better more informative backtrace with mentioned s
I found a very simple way to reproduce segfault in nodejs when using browserify.
Take Debian Bookworm i386, upgraded in to last versions of packages
with this repos:
deb http://deb.debian.org/debian bookworm contrib main non-free-firmware
deb-src http://deb.debian.org/debian bookworm contrib main
It's interesting that problem is reproducible in Debian Bookworm i386
in other cases when building node packages from source.
The same problem with browserify occurs when building source package
node-prop-types_15.8.1+~15.7.5-2.
As earlier, I took Debian Bookworm i386 with repos:
deb http://deb.de
y good (packages
originating from node-chai are incomplete in this case), but at the
moment it seems suitable for me. Maybe I'll try other workarounds you
described here later.
пн, 15 июл. 2024 г. в 12:42, Jérémy Lal :
>
>
>
> Le lun. 15 juil. 2024 à 11:27, Сергей Сёмин a écrit :
>>
I tried to give maximum resources to my VM with Debian Bookworm i386
(recently upgraded to Debian Sid).
I gave 8 GB RAM in VM settings but because of i386 limitations only
4GB actually available in VM.
The problem remains:
root@debian-bookworm-i386:~/node-chai-4.3.7~ds1+~cs9.7.21# free -h
Hi!
Just now I upgraded my existing Debian Bookworm i386 installation to
Debian Sid using this repositories:
deb http://deb.debian.org/debian unstable contrib main non-free-firmware
deb-src http://deb.debian.org/debian unstable contrib main non-free-firmware
Now I have these versions of packages o
Hi!
Rouca, thank you for installing the latest version of imagemagick in
the Debian FTP archive!
As I see, the new version of imagemagick with fully fixed
CVE-2023-34151 is 8:6.9.13.12+dfsg1-1. And now it is already included
in sid distribution:
https://packages.debian.org/sid/imagemagick
I have
Hi!
Later in this comment I wrote description of way how to reproduce
CVE-2023-34151 in recent imagemagick from Debian Bookworm.
Rouca, plese, let me know, is it enough to start investigating of the problem?
Goto page https://app.vagrantup.com/debian (mentioned here
https://wiki.debian.org/Teams
Unfortunately, I couldn't create patch for imagemagick from Debian
Bookworm. So I sent only patch for imagemagick from Debian Buster.
вт, 14 мая 2024 г. в 15:38, Сергей Сёмин :
> Hello!
> Upstream developers of ImageMagick6 fixed CVE-2023-34151 for mvg after all.
> See more info h
Hello!
Upstream developers of ImageMagick6 fixed CVE-2023-34151 for mvg after all.
See more info here:
https://github.com/ImageMagick/ImageMagick/issues/6341#issuecomment-2108156142
I discovered final list of commits fixing problem:
-
https://github.com/ImageMagick/ImageMagick6/commit/75ebd9975f6b
Initially I wrote only about Bookworm. But it is not only Bookworm problem.
For example, I have also repeat steps from
https://docs.google.com/document/d/1zjM5MvfFYC317PEPY4_4WRi0hOdpM766FyqpvOmeE90/edit?usp=sharing
in the environment of vagrant image debian/buster64 v10.20231211.1
(available here:
13 matches
Mail list logo
