Hello. I have a problem with WebPositive after update to in progress “Beta 6” (hrev59866). When I open it in terminal, it don’t start and give this error:
runtime_loader: /boot/system/lib/libWebKitLegacy.so.1.10.0: Could not resolve symbol ‘_ZN9Inspector22InspectorDebuggerAgent25didCreateInternalFunctionERN3JSC16InternalFunctionE’ resolve symbol “_ZN9Inspector22InspectorDebuggerAgent25didCreateInternalFunctionERN3JSC16InternalFunctionE” returned: -2147478780 runtime_loader: /boot/system/lib/libWebKitLegacy.so.1.10.0: Troubles relocating: Symbol not found
I try to completely uninstall haikuwebkit and webpositive, delete cache, and install clean again from server. The versions are haikuwebkit-1.10.0-2-x86_64 and webpositive-r1~beta6_hrev59866_73-1, but error is exactly the same.
the package in the repository is broken / its too early to update from there??
FWIW, a ‘symbol’ in this context often refers to named variable, function definition, etc in the code for the program. So the error likely means that the main program EITHER cannot find the ‘shared object’ (so) called libWebKitLegacy.so.1.10.0 (might mean that only a newer version is present) OR that having found it cannot find something in it that it expected to.
It looks like runtime_loader (not sure if that’s part of Haiku or WebPositive) tried to “resolve symbol” and got a large negative number as a result… (-17FFFECFCh or FFFFECFCh).
The problem may be similar in nature to one which was described in this thread:
It might be necessary for somebody to rebuild the package.
@Istarian, yes, the runtime_loader is part of Haiku, it’s the component which load ELF files (executable and shared libs).
Here, while trying to load libWebKitLegacy.so.1.10, while loading shared libs depencies of the WebPositive executable, failed to resolve the symbol Inspector::InspectorDebuggerAgent::didCreateInternalFunction(JSC::InternalFunction&).
And the FFFFECFCh large number is just an error code, which is even display: Symbol not found.
I don’t think WebPositive has inspector debugger support, so maybe something is broken indeed here. Maybe while building libWebKitLegacy is was enabled by error while the feature is expected from another library (libJavaScriptCore.so, maybe), I really dunno.
Anyway, sounds like it’s too early, yes, or that nightly is not stable regarding WebPositive.
But if you get it while update from latest nightly (via “current” repo), then such thing can happened because not all packages are perfectly on same level of fixes and updates.
I just did a quick check on my main development VM; I have the exact same HaikuWebKit version (but a nightly build, not beta6) installed and everything works there.
I’m writing this from WebPositive on a new install of R1/beta6 on x86_64 with all the latest updates and there was no issue starting the browser, including from the command line, for me.