Opened 14 years ago
Closed 14 years ago
#29118 closed defect (fixed)
htop @0.8.3_1 - htop crash when trying to use the SortBy (F6) function
Reported by: | olivier.hervieu@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | ||
Port: | htop |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
On Mac OS 10.6, trying to sort process thanks to the SortBy function crash htop with the following message :
htop 0.8.2.1 aborted. Please report bug at http://htop.sf.net
This behavior is observed with the two shortcuts of the SortBy function (">" and "F6")
The second strange things is that both the man and the messages refers to the 0.8.2 version, but the version displayed by port search htop is 0.8.3.
Change History (3)
comment:1 follow-up: 2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|---|
Status: | new → assigned |
Replying to ryandesign@…:
Replying to olivier.hervieu@…:
htop 0.8.2.1 aborted. Please report bug at http://htop.sf.net
And did you report the bug at that URL?
Actually, scratch that. It appears that they don't want Mac bug reports. I see that this has been reported on the htop mailing list (with no reply) and I think it's the same as this bug report in their issue tracker (closed invalid: htop not supported on Mac OS X).
The htop we have in MacPorts actually uses code from someone else to make htop Mac-compatible. The issue you're reporting is also reported there, and there is a patch. I'll see if I can put that in the Portfile.
comment:3 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed this and several other problems in r77804. The version number of the port has also been corrected: it's version 0.8.2.1. The manual still shows 0.8.2 since the manual did not need to be updated between 0.8.2 and 0.8.2.1.
Replying to olivier.hervieu@…:
And did you report the bug at that URL?