Opened 6 years ago
Closed 3 years ago
#32345 closed defect (fixed)
mdk: MMIX mixvm causes seg fault on Mac OS X 10.6
| Reported by: | wferris@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | cooljeanius (Eric Gallager), ryandesign (Ryan Schmidt) | |
| Port: | mdk |
Description
I have installed the port MDK and when I try to run the mixvm I get a seg fault. I have attached the crash report.
Attachments (1)
Change History (8)
Changed 6 years ago by wferris@…
comment:1 Changed 6 years ago by ryandesign (Ryan Schmidt)
- Owner changed from macports-tickets@… to aconchillo@…
- Summary changed from MMIX mixvm (mdk) causes seg fault on Mac OS X 10.6 to mdk: MMIX mixvm causes seg fault on Mac OS X 10.6
Don't forget to Cc the port's maintainer.
comment:2 Changed 6 years ago by aconchillo@…
I've been able to reproduce the issue. But unable to fix it. I think it will need some work from the developer.
Here's the bug:
comment:3 follow-up: ↓ 4 Changed 5 years ago by jmroot (Joshua Root)
The first thing to do would be to update the port to 1.2.6 and see if the problem persists in that version.
comment:4 in reply to: ↑ 3 Changed 5 years ago by aconchillo@…
Replying to jmr@…:
The first thing to do would be to update the port to 1.2.6 and see if the problem persists in that version.
I am not planning to maintain this port anymore. Actually, it's been a while since I don't use a Mac. 10 months ago I could try it in a laptop I borrowed.
So, it doesn't make sense to wait for me.
Here's the solution pointed by the author:
https://savannah.gnu.org/bugs/index.php?36183#comment1
In any case, you are right in that it should be updated to the newer version.
comment:5 Changed 3 years ago by ryandesign (Ryan Schmidt)
- Owner changed from aconchillo@… to macports-tickets@…
comment:7 Changed 3 years ago by ryandesign (Ryan Schmidt)
- Cc ryandesign@… added
- Resolution set to fixed
- Status changed from new to closed
mdk has been updated to 1.2.8; please re-open if this problem persists after upgrading the port.
crash report