Since this does seem to have fixed the problem on macOS, I wondered why it might be a problem. It looks to me like the libc++ being built is built in Release+Asserts mode even when I ask for v8 to be built in debug mode. I wonder if this ends up being the problem when debug code is expecting one thing, but instead it is getting a release version.
In any case, I think that I am going to look into modifying the GN build for v8 to allow using the default or "system" libc++ instead of just being able to use the "default" c++ standard library or the custom libc++ library. If you or anyone else can give me some guidance on that, I'd be happy to contribute it back. I'm sure I can't be the only person this has bitten and frustrated. Thanks again for all the help! On Thursday, July 18, 2019 at 9:52:49 AM UTC-4, Jakob Gruber wrote: > > > On Thu, Jul 18, 2019 at 3:10 PM Christopher Nelson <nadias...@gmail.com > <javascript:>> wrote: > >> I appreciate that info, and I have read it. However, that is very >> unlikely to be the problem here. In this case I am not passing any C++ ABI >> objects between libraries, I'm just creating a new isolate. The >> reproduction is so minimal and so simple that is seems very unlikely that >> libc++ is at fault here. It happens deep inside the isolate initialization. >> > > I see. It sounds like you have a full repro to share; could you perhaps > open a bug at crbug.com/v8/new, include the repro, and I will try to have > a look next week. > > >> >> On Thursday, July 18, 2019 at 8:43:42 AM UTC-4, Jakob Gruber wrote: >>> >>> On Thu, Jul 18, 2019 at 2:32 PM Christopher Nelson <nadias...@gmail.com> >>> wrote: >>> >>>> I'm not using the same exact libc++, no. I don't have a problem doing >>>> that, but I'd like to link v8 against MY libc++ instead of linking my app >>>> against v8's libc++. The reason is: I am compiling against a number of >>>> libraries, all of which are compiled against my libc++. Trying to change >>>> them all to compile against V8's libc++ is probably not possible. >>>> >>>> I'm also a little suspicious that libc++ is the problem here because it >>>> works fine in release; which I would expect to be _more_ sensitive. In any >>>> case, if you can tell me how or point me to instructions on how to tell V8 >>>> which libc++ to use I will very happily implement that. >>>> >>> >>> I assume building with a libcxx that is neither the system libcxx nor >>> V8's custom libcxx will need manual work. I'm not an expert on this either, >>> I've just seen folks run into this fairly frequently in recent times. >>> >>> Here's where all of my infos come from: https://crbug.com/v8/9150#c2. >>> Maybe this will help clarify. >>> >>> -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/b77de9a9-2b84-4726-a411-5eb3a4eb5894%40googlegroups.com.
