Opened 13 years ago
Closed 13 years ago
#29761 closed defect (invalid)
htop doesn't work after install
| Reported by: | inanc64@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: | htop |
Description (last modified by mf2k (Frank Schima))
When I run htop after install I get this error:
htop(27913) malloc: *** error for object 0x100cf0: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug
Specs: Snow Leopard 10.6.7
Change History (6)
comment:1 Changed 13 years ago by inanc64@…
| Cc: | inanc64@… added |
|---|
comment:2 Changed 13 years ago by mf2k (Frank Schima)
| Cc: | inanc64@… removed |
|---|---|
| Description: | modified (diff) |
| Port: | htop added |
comment:3 Changed 13 years ago by mf2k (Frank Schima)
What makes you think this is a Macports bug and not an htop bug? Perhaps you should bring it up with the developer(s).
comment:4 follow-up: 6 Changed 13 years ago by inanc64@…
I don't know, but it seems to be working now. I haven't done anything.
comment:5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|
Note that "htop" in MacPorts is actually htop-osx; you should report any issues there, not to the developers of the original htop, who don't know anything about the Mac fork and don't really seem to be interested in it either (c.f. when this problem was reported to them before)
In fact the problem was reported to htop-osx in December 2009 and the solution listed there is that we need to build it 32-bit. Hmm.
However, this was supposedly fixed in MacPorts 21 months ago; see #21036. Are you sure your ports are up to date? What version of htop was installed? ("port installed htop") What version of MacPorts are you running? ("port version") Have you selfupdated lately? ("sudo port selfupdate")
comment:6 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Replying to inanc64@…:
I don't know, but it seems to be working now. I haven't done anything.
Then I'll close it.
Cc Me!