Re: [v8-users] Segment fault when update v8..

2020-03-01 Thread YQ Tian
Thank you very much, the option use_custom_libcxx=false can indeed use the c ++ standard library instead of the internal c ++ library of v8, but when compiling, torque requires a higher version of glibc. Due to program reasons, I cannot link the higher version of the c ++ library. Can I compi

Re: [v8-users] Segment fault when update v8..

2020-02-29 Thread YQ Tian
Thank you very much, the parameters can indeed use the c ++ standard library instead of the internal c ++ library of v8, but when compiling, a presumably called torque requires a higher version of glibc. Due to program reasons, I cannot link the higher version of the c ++ library. Can I compile

Re: [v8-users] Segment fault when update v8..

2020-02-29 Thread Ben Noordhuis
On Sat, Feb 29, 2020 at 5:26 AM YQ Tian wrote:> > Thank you for your reply. It is currently found that when I upgrade v8 to > 6.8, the dynamic_cast function of my other dynamic library will call the > has_unambiguous_public_base function in the v8 library. Normally, the C ++ > standard library

Re: [v8-users] Segment fault when update v8..

2020-02-28 Thread YQ Tian
Thank you for your reply. It is currently found that when I upgrade v8 to 6.8, the dynamic_cast function of my other dynamic library will call the has_unambiguous_public_base function in the v8 library. Normally, the C ++ standard library should be called. This phenomenon is very strange. I Com

Re: [v8-users] Segment fault when update v8..

2020-02-28 Thread YQ Tian
Thank you for your reply. It is currently found that when I upgrade v8 to 6.8, the dynamic_cast function of my other dynamic library will call the has_unambiguous_public_base function in the v8 library. Normally, the C ++ standard library should be called. This phenomenon is very strange. I Com

Re: [v8-users] Segment fault when update v8..

2020-02-28 Thread YQ Tian
Thank you for your reply. It is currently found that when I upgrade v8 to 6.8, the dynamic_cast function of my other dynamic library will call the has_unambiguous_public_base function in the v8 library. Normally, the C ++ standard library should be called. This phenomenon is very strange. I Com

Re: [v8-users] Segment fault when update v8..

2020-02-28 Thread Jakob Kummerow
6.8 is a year and a half before pointer compression though. Which also means that 6.8 is obsolete and unsupported. On Fri, Feb 28, 2020 at 12:14 PM Ben Noordhuis wrote: > On Fri, Feb 28, 2020 at 4:05 AM YQ Tian wrote: > > > > v8 version 6.8.275.32 > > > > Hi all! > > > > > > When I upgrade the

Re: [v8-users] Segment fault when update v8..

2020-02-28 Thread Ben Noordhuis
On Fri, Feb 28, 2020 at 4:05 AM YQ Tian wrote: > > v8 version 6.8.275.32 > > Hi all! > > > When I upgrade the v8 version, my program crashes. My program statically > links the v8 library and also uses another dynamic library. The dynamic > library will call the dynamic_cast function, to see the