mirrors/OpenRCT2
1
0
Fork 0
mirror of https://github.com/OpenRCT2/OpenRCT2 synced 2026-02-01 19:25:12 +01:00
Code Issues Releases Wiki Activity

https, macos

Margen67
2021-04-18 06:19:34 -10:00
parent 79cd1e4cc9
commit 69e6e80281
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Debugging-OpenRCT2-on-OSX.md → Debugging-OpenRCT2-on-macOS.md

@@ -1,11 +1,10 @@
# The information on this page is very outdated and concerns the mingw target only. Just use `lldb` for native builds.
When debugging with `winedbg`, you probably found out that you can't:
1. Set break/watch points (not even using the literal address),
2. Use debug symbols.
To debug OpenRCT2 with these features, a particularly strange setup has to be used. I've been searching for ways to debug cross-compiled MinGW executables, and finally found this StackOverflow post: http://stackoverflow.com/questions/3720434/can-gdb-be-used-on-a-cross-compiled-win32-application-on-the-target-platform
To debug OpenRCT2 with these features, a particularly strange setup has to be used. I've been searching for ways to debug cross-compiled MinGW executables, and finally found this StackOverflow post: https://stackoverflow.com/questions/3720434/can-gdb-be-used-on-a-cross-compiled-win32-application-on-the-target-platform
In summary, the setup is as follows:
@@ -25,7 +24,7 @@ After this, you can set breakpoints as you like!
First, we compile gdb. To do this, we need a gcc compiler and the gdb source code. On later versions on OSX, gcc has been replaced with clang. So use a gcc compiler installed with MacPorts or HomeBrew. I used MacPorts' gcc49 package.
1. Grab the gdb source from GNU: http://www.gnu.org/software/gdb/download/. I used version 7.8.
1. Grab the gdb source from GNU: https://www.gnu.org/software/gdb/download/. I used version 7.8.
2. Configure gdb using the following command **in the root directory**. That is, in the directory gcc-[version], **and not gcc-[version]/gcc**: