#8135: Support debug info in separate file -------------------------------------+---------------------------- Reporter: bonefish | Owner: anevilyak Type: enhancement | Status: in-progress Priority: low | Milestone: R1 Component: Applications/Debugger | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 1 | Platform: All -------------------------------------+---------------------------- Comment (by bonefish): The `objcopy` bug might be worth a bug report. :-) Regarding your first caveat, if you used Haiku's build system to build the release and the debug version of the file, problems are to be expected, since one is built with and the other without optimization. In the Linux world usually the release versions are built with both optimization and debug info (and where possible, the debug info is split into another file/package). The result is not optimal for debugging -- due to the optimization inlining and reordering code -- but after all it is a release build. Regarding the resources, the Haiku build system could automate the step, respectively add the resources after extracting the debug info in the first place. Regarding your patch: * Not important, but I would swap the `_GetDebugInfoPath()` parameters. Output parameters usually come last (though there are exceptions when there are other parameters with default values). * I don't know why you made the `dirLocations` array `int16`. It should be `directory_which`. Also the `-1` element is not needed. The number of elements is `sizeof(dirLocations) / sizeof(dirLocations[0])`. Moreover the array could be const. -- Ticket URL: <http://dev.haiku-os.org/ticket/8135#comment:17> Haiku <http://dev.haiku-os.org> Haiku - the operating system.