Opened 12 years ago

Last modified 8 days 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.1
Component: System/runtime_loader Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: All


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 (4)

comment:1 by anevilyak, 12 years ago

The problem is it's not the runtime loader that makes that determination. 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 by mmadia, 12 years ago

just to note for clarity, R5 Compatibility Mode usually occurs when is called as,, or

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

comment:3 by axeld, 3 years ago

Owner: changed from axeld to nobody
Status: newassigned

comment:4 by pulkomandy, 8 days ago

Milestone: R1R1.1
Note: See TracTickets for help on using tickets.