Opened 3 months ago
Closed 3 weeks ago
#69360 closed defect (fixed)
nano @7.2: on 10.4.11 "Bus error"
| Reported by: | garoffoli (garoffoli) | Owned by: | aeiouaeiouaeiouaeiouaeiouaeiou |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.9.1 |
| Keywords: | tiger ppc | Cc: | |
| Port: | nano |
Description
Machine: PowerBook G4 "15 on Mac OS X Tiger 10.4.11
Compiling works fine, but trying to start nano complains about a "Bus error"
Attachments (1)
Change History (6)
comment:1 follow-up: 2 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | nano@7.2 on 10.4.11 "Bus error" → nano @7.2: on 10.4.11 "Bus error" |
|---|
Changed 3 months ago by garoffoli (garoffoli)
| Attachment: | nano.crash.log added |
|---|
comment:2 Changed 3 months ago by garoffoli (garoffoli)
Replying to ryandesign:
A bus error is a crash. Did Mac OS X generate a crash log file? In Tiger crash logs would be stored in ~/Library/Logs/CrashReporter. If there is a log for nano's crash there, please attach it. Maybe it helps pinpoint the problem.
Just uploaded it!
comment:3 follow-up: 4 Changed 3 months ago by jmroot (Joshua Root)
It's relying on the newer realpath behaviour of allocating memory for you when passed a NULL resolved_name pointer.
comment:4 Changed 3 months ago by garoffoli (garoffoli)
Replying to jmroot:
It's relying on the newer realpath behaviour of allocating memory for you when passed a NULL resolved_name pointer.
This comment helped me on how to fix it and make it run, by adding
PortGroup legacysupport 1.1
to the nano Portfile and recompiling it.
comment:5 Changed 3 weeks ago by aeiouaeiouaeiouaeiouaeiouaeiou
| Owner: | set to aeiouaeiouaeiouaeiouaeiouaeiou |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
A bus error is a crash. Did Mac OS X generate a crash log file? In Tiger crash logs would be stored in ~/Library/Logs/CrashReporter. If there is a log for nano's crash there, please attach it. Maybe it helps pinpoint the problem.