Opened 10 years ago

Last modified 23 months ago

#3576 assigned enhancement

runtime_loader : display which file triggered R5 compatibility mode in syslog

Reported by: mmadia Owned by: nobody
Priority: normal Milestone: R1
Component: System/runtime_loader Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

runtime_loader should be able to print to syslog the imagename that requested the compatibility-mode lib.

This will help to identify files that are not haiku-binaries

Change History (3)

comment:1 Changed 10 years ago by anevilyak

The problem is it's not the runtime loader that makes that determination. libnetwork.so does that directly by looking at what soname it was loaded as, and as such has no actual knowledge of which part of the linker chain was the culprit. This might be doable in the runtime loader but at least right now it plays no part in the compat mechanism.

comment:2 Changed 10 years ago by mmadia

just to note for clarity, R5 Compatibility Mode usually occurs when libnetwork.so is called as libbind.so, libsocket.so, or libnet.so.

This occurs when loading a binary or lib that was built in a version of BeOS.

comment:3 Changed 23 months ago by axeld

Owner: changed from axeld to nobody
Status: newassigned
Note: See TracTickets for help on using tickets.