Could you try first to apply https://github.com/nodejs/node/commit/c60780ff52
And see if the reject are bad ?
Bastien
Le lun. 20 sept. 2021 à 19:15, Ondrej Zary a écrit :
>
>
>
> On Monday 20 September 2021 19:31:56 Bastien ROUCARIES wrote:
> > Le lun. 20 sept. 2021 à 17:28, Jérémy Lal a
Le lun. 20 sept. 2021 à 17:15, Ondrej Zary a écrit :
>
> On Monday 20 September 2021 16:56:18 Bastien ROUCARIES wrote:
> > Le lun. 20 sept. 2021 à 14:24, Ondrej Zary a écrit :
> > >
> > > On Monday 20 September 2021, Bastien ROUCARIES wrote:
> > > > Could you try to apply
> > > >
> > > >
On Monday 20 September 2021, Bastien ROUCARIES wrote:
> Could you try to apply
>
> https://github.com/nodejs/node/commit/aa4611cccbcb197df51a9f7056d019005d91acf4
>
> I think it describe that you see
Does not apply, unfortunately. There's no node_dir.cc file and also no
BaseObjectPtr
Could you try to apply
https://github.com/nodejs/node/commit/aa4611cccbcb197df51a9f7056d019005d91acf4
I think it describe that you see
Bastien
Le lun. 20 sept. 2021 à 12:51, Ondrej Zary a écrit :
>
> > Ok are you on IRC ? I am as rouca on #debian-js channel
>
> No, I'm not.
>
> > Install the
> And try to rebuild the whole libuv and nodejs with -fstack-protector-all
Does not print anything other than Segmentation fault.
--
Ondrej Zary
> add --track-origins=yes to valgrind
Does not seem to change anything:
# runuser -u gitlab -- sh -c 'valgrind --trace-children=yes --track-origins=yes
yarnpkg install'
==6122== Memcheck, a memory error detector
==6122== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==6122==
Le lun. 20 sept. 2021 à 10:39, Ondrej Zary a écrit :
>
> > Ok now try to run the whole thing against valgrind...
> Seems that valgrind does not work with asan:
>
> $ LD_PRELOAD=/usr/lib/i386-linux-gnu/libasan.so.5.0.0 valgrind yarnpkg install
> ==752== Memcheck, a memory error detector
> ==752==
Le lun. 20 sept. 2021 à 10:20, Bastien ROUCARIES
a écrit :
>
> Le lun. 20 sept. 2021 à 10:15, Ondrej Zary a écrit :
> >
> > libuv libuv1:i386 1.24.1-1+deb10u1 with -fsanitize=address,undefined:
> >
> > yarn install v1.13.0
> > [1/5] Validating package.json...
> > [2/5] Resolving packages...
> >
Le lun. 20 sept. 2021 à 10:15, Ondrej Zary a écrit :
>
> libuv libuv1:i386 1.24.1-1+deb10u1 with -fsanitize=address,undefined:
>
> yarn install v1.13.0
> [1/5] Validating package.json...
> [2/5] Resolving packages...
> [3/5] Fetching packages...
>
Le dim. 19 sept. 2021 à 21:39, Bastien ROUCARIES
a écrit :
>
> Le dim. 19 sept. 2021 à 21:36, Ondrej Zary a écrit :
> >
> > I've reinstalled nodejs and libnode64 back to original Buster
> > 10.24.0~dfsg-1~deb10u1 and upgraded libuv1 to
> > libuv1_1.34.2-1~bpo9+1_i386.deb from
Le dim. 19 sept. 2021 à 21:36, Ondrej Zary a écrit :
>
> I've reinstalled nodejs and libnode64 back to original Buster
> 10.24.0~dfsg-1~deb10u1 and upgraded libuv1 to libuv1_1.34.2-1~bpo9+1_i386.deb
> from http://snapshot.debian.org
>
> It still segfaults!
>
> So it seems that the problem is
On Sunday 19 September 2021 20:13:47 Bastien ROUCARIES wrote:
> Hi,
>
> So you work on oldstable.
>
> Could you check for stable/testing/unstable/experimental ? And mark
> the bug with found /not found.
Unfortunately I can't. I'm trying to get gitlab 11.11.8+dfsg-1+fto10+2 to work.
Then I can
Le dim. 19 sept. 2021 à 19:37, Jérémy Lal a écrit :
>
>
>
> Le dim. 19 sept. 2021 à 20:18, Bastien ROUCARIES
> a écrit :
>>
>> Hi,
>>
>> So you work on oldstable.
>>
>> Could you check for stable/testing/unstable/experimental ? And mark
>> the bug with found /not found.
>>
>
> Interestingly,
Le dim. 19 sept. 2021 à 20:18, Bastien ROUCARIES <
roucaries.bast...@gmail.com> a écrit :
> Hi,
>
> So you work on oldstable.
>
> Could you check for stable/testing/unstable/experimental ? And mark
> the bug with found /not found.
>
>
Interestingly, the copy of zlib in nodejs source has several
Hi,
So you work on oldstable.
Could you check for stable/testing/unstable/experimental ? And mark
the bug with found /not found.
Thanks
Bastien
Le dim. 19 sept. 2021 à 18:03, Ondrej Zary a écrit :
>
> There's no such patch in 10.24.0~dfsg-1~deb10u1
>
> --
> Ondrej Zary
There's no such patch in 10.24.0~dfsg-1~deb10u1
--
Ondrej Zary
Le dim. 19 sept. 2021 à 17:40, Ondrej Zary a écrit :
>
> Upstream node rebuilt in Debian works. So it's not a compiler or libc problem.
Does removing the debian patch
large_pages_assembly_gnu_stack.patch
Changes something ?
Bastien
> The Debian (buster) i386 version 10.24.0~dfsg-1~deb10u1
Upstream node rebuilt in Debian works. So it's not a compiler or libc problem.
The Debian (buster) i386 version 10.24.0~dfsg-1~deb10u1 already contains SSE2
instructions - it does not work on Pentium 3:
$ node
Illegal instruction
So I doubt that changing -march would help.
--
Ondrej Zary
Le dim. 19 sept. 2021 à 16:33, Ondrej Zary a écrit :
>
> upstream (strings in bin/node), seems to be statically linked:
> gcc 6.3.1
> libc 2.17 according to https://github.com/nodejs/unofficial-builds/
> build log found at
> https://unofficial-builds.nodejs.org/logs/202102231620-v10.24.0/x86.log
19 matches
Mail list logo
