-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GDB should not have been upgraded past 8.0.1 on recent macOS systems #31424
Comments
|
Without upstream or user guidance if it builds and the
We're not going to do conditional downgrades so we'd need to settle on a version. We're also not prepared to pin a formula on one version indefinitely; there would need to be some kind of reassurance that the formula will be upgradeable again in the not-overly-distant future. Your last sentence there somewhat concerns me because clearly upstream are having some issues testing with macOS, and I'm not sure quite how you propose we ensure a new release has been "properly tested" on a current macOS release without investing a significant chunk of time into doing so ourselves, which is a burden I'm not willing to impose on myself and/or the rest of the maintainer team. I would appreciate some clarity as to what this proper testing would look like & where it would come from. |
Looking at the above-linked bug reports, it is clear that the problem(s) has (have) not been identified, and that it is not even sure they are specific to 8.1, as other reports this bug for Sierra on an earlier version of gdb. Like @DomT4, I don't think we want to roll back (which is a huge annoyance for everyone) unless there is a fix coming / timeline for a solution. And it seems we're far from that. |
I'm not sure you guys understand. GDB-8.1 and GDB-8.1.1 are both entirely useless and CAN NOT WORK AT ALL on macOS (since probably 10.11, maybe even 10.10, and definitely not on 10.12 or 10.13). The fact that they even compile on macOS is a mistake (the builds should have been purposefully broken to prevent this kind of tail-chasing nonsense). It is also pointless to even look at these or any newer release until after the bug reports I referenced are marked as fixed and those fixes are incorporated into a new release. I can't give you any hints about timelines for when GDB might work on macOS again -- I'm not a maintainer. I did note in reading the GDB mailing list archives that there is code available that should include the necessary fixes, but there are disagreements and disillusionment surrounding its copyright assignment, and also at the moment there are apparently no macOS systems available to GDB maintainers. I don't think it's worth adding any additional GDB testing for However it is possible to continue to use GDB-8.0.1 on macOS (to the limited degree that it has always worked on OS X and now macOS). As I see it this leaves two possible reasonable choices for Homebrew:
It would be unreasonable to continue to offer a known-to-be-broken and useless GDB to Homebrew users. I would assume there is some non-empty set of Homebrew users (other than me) who also would like to sometimes use GDB, but of course I have no idea how many users that might be. I do note that it seems common for people to suggest Homebrew as the answer to how to get GDB on macOS. The fact that one well read and well referenced post on StackOverflow gives instructions on how to manually downgrade GDB using Homebrew is also something interesting and relevant to keep in mind (though it is definitely not a real solution to this problem). I have not had the chance to see if 8.1 or 8.1.1 works on an older OS X -- I no longer have access to any such system, but I suppose it is possible it may work, e.g. on say 10.6.8. If Homebrew supports 10.6.8, and if GDB-8.1.1 works there, then maybe there is some way to continue to offer the newer GDB for such older OS X releases while at the same time sticking to 8.0.1 on newer macOS systems. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
brew install
(orupgrade
,reinstall
) a single, official formula (not cask)? If it's a generalbrew
problem please file this issue at Homebrew/brew: https://github.com/Homebrew/brew/issues/new/choose. If it's abrew cask
problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.brew update
and can still reproduce the problem?To help us debug your issue please explain:
On a system running macOS 10.13.x I tried to use
gdb
after runningbrew upgrade
where gdb was upgraded from 8.0.1 to 8.1 (then more recently to 8.1.1)Upgrades of GDB since 8.1 fail to run inferior processes on any recent macOS:
And here you can see the older release still works well enough to actually start an inferior process:
GDB should have been downgraded back to 8.0.1 when macOS updates made the newer releases stop working. Perhaps 8.0.1 will also stop working entirely with some new macOS release, in which case it should be deprecated and removed (at least for macOS systems where it cannot work).
Please downgrade GDB again (at least for macOS releases where 8.1 and newer are impossibly broken) and then see the following GDB bug reports and don't upgrade GDB again until those GDB bug reports are fixed and closed and the fixes are available in a new release that is properly tested on a current macOS release!
https://sourceware.org/bugzilla/show_bug.cgi?id=22960
https://sourceware.org/bugzilla/show_bug.cgi?id=20266
The text was updated successfully, but these errors were encountered: