Bug 228604 - devel/memleax: Update to 1.1.1
Summary: devel/memleax: Update to 1.1.1
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Tobias Kortkamp
URL: https://github.com/WuBingzheng/memlea...
Keywords: patch
Depends on:
Blocks:
 
Reported: 2018-05-30 12:43 UTC by Tobias Kortkamp
Modified: 2018-10-26 22:30 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (guy.tabrar)

Attachments
memleax.diff (1.26 KB, patch)
2018-05-30 12:43 UTC, Tobias Kortkamp 		tobik: maintainer-approval? (guy.tabrar)
 Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Kortkamp freebsd_committer freebsd_triage 2018-05-30 12:43:00 UTC 
Created attachment 193839 [details]
memleax.diff

Hi,

this updates memleax to the latest version and fixes some style issues.
I'd also like to request maintainership to keep this updated if that's ok.

Thanks!
Comment 1 commit-hook freebsd_committer freebsd_triage 2018-10-11 12:23:55 UTC 
A commit references this bug:

Author: tobik
Date: Thu Oct 11 12:23:38 UTC 2018
New revision: 481818
URL: https://svnweb.freebsd.org/changeset/ports/481818

Log:
  devel/memleax: Take maintainership

  PR:		228604
  Approved by:	maintainer timeout (4 months)

Changes:
  head/devel/memleax/Makefile
Comment 2 Pavel Timofeev 2018-10-16 11:30:10 UTC 
Any update on this?

I'd add i386 to ONLY_FOR_ARCHS as v1.1.0 release notes says it supports this
https://github.com/WuBingzheng/memleax/releases
Comment 3 Tobias Kortkamp freebsd_committer freebsd_triage 2018-10-16 11:35:27 UTC 
(In reply to timp87 from comment #2)
AFAICT Memleax (1.0.3 as well as 1.1.1) is broken and doesn't detect leaks
correctly.  It will be removed from the ports tree on 2018-10-31 unless
someone can fix it.
Comment 4 Pavel Timofeev 2018-10-16 14:13:17 UTC 
Has the problem been reported to upstream?
Comment 5 Tobias Kortkamp freebsd_committer freebsd_triage 2018-10-16 14:20:55 UTC 
Nope.