aa4b5749d6
* Previously PE binaries would trigger the "incorrectly executable" dialog. Now we get a special message for B_LEGACY_EXECUTABLE and B_UNKNOWN_EXECUTABLE * Legacy at the moment is a R3 x86 PE binary. This could be extended to gcc2 binaries someday far, far, down the road though * The check for legacy is based on a PE flag I see set on every R3 binary (that isn't set on dos ones) * Unknown is something we know *is* an executable, but can't do anything with (such as an MSDOS or Windows application) * No performance drops as we do the PE scan last * Tested on x86 and x86_gcc2 |
||
|---|---|---|
| .. | ||
| arch | ||
| posix | ||
| architecture_private.h | ||
| commpage_defs.h | ||
| computed_asm_macros.h | ||
| ddm_userland_interface_defs.h | ||
| device_manager_defs.h | ||
| directories.h | ||
| disk_device_types.h | ||
| elf32.h | ||
| elf64.h | ||
| elf_common.h | ||
| extended_system_info_defs.h | ||
| find_directory_private.h | ||
| generic_syscall_defs.h | ||
| image_defs.h | ||
| node_monitor_private.h | ||
| pe_common.h | ||
| real_time_data.h | ||
| safemode_defs.h | ||
| scheduler_defs.h | ||
| signal_defs.h | ||
| spinlock_contention.h | ||
| symbol_versioning.h | ||
| syscall_process_info.h | ||
| syscalls.h | ||
| system_info.h | ||
| system_profiler_defs.h | ||
| thread_defs.h | ||
| tls.h | ||
| user_mutex_defs.h | ||
| user_runtime.h | ||
| user_thread_defs.h | ||
| user_timer_defs.h | ||
| vfs_defs.h | ||
| vm_defs.h | ||