mirror of
https://git.FreeBSD.org/ports.git
synced 2025-01-23 09:10:43 +00:00
- Improve COMMENT text, add LICENSE
- Convert one patch file to MAKE_ARGS - Stagify, dismiss NOPORTDOCS check - Cleanup pkg-descr and pkg-message
This commit is contained in:
parent
a5794020d8
commit
de1b6c2e18
Notes:
svn2git
2021-03-31 03:12:20 +00:00
svn path=/head/; revision=340555
@ -9,24 +9,20 @@ DISTNAME= ${PORTNAME}
|
||||
EXTRACT_SUFX= .tgz
|
||||
|
||||
MAINTAINER= onatan@gmail.com
|
||||
COMMENT= Utility to dump process memory
|
||||
COMMENT= Utility to dump memory of a running process
|
||||
|
||||
LICENSE= GPLv2
|
||||
|
||||
WRKSRC= ${WRKDIR}/${PORTNAME}
|
||||
USES= perl5
|
||||
USE_PERL5= run
|
||||
MAKE_ARGS= CC="${CC}" CFLAGS="${CFLAGS}"
|
||||
|
||||
CFLAGS+= ${CPPFLAGS}
|
||||
WRKSRC= ${WRKDIR}/${PORTNAME}
|
||||
|
||||
NO_STAGE= yes
|
||||
do-install:
|
||||
${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${PREFIX}/bin
|
||||
${INSTALL_SCRIPT} ${WRKSRC}/mffind.pl ${PREFIX}/bin
|
||||
.if !defined(NOPORTDOCS)
|
||||
${MKDIR} ${DOCSDIR}
|
||||
${INSTALL_DATA} ${WRKSRC}/README ${DOCSDIR}
|
||||
.endif
|
||||
|
||||
post-install:
|
||||
@${CAT} ${PKGMESSAGE}
|
||||
${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${STAGEDIR}${PREFIX}/bin
|
||||
${INSTALL_SCRIPT} ${WRKSRC}/mffind.pl ${STAGEDIR}${PREFIX}/bin
|
||||
@${MKDIR} ${STAGEDIR}${DOCSDIR}
|
||||
${INSTALL_DATA} ${WRKSRC}/README ${STAGEDIR}${DOCSDIR}
|
||||
|
||||
.include <bsd.port.mk>
|
||||
|
@ -1,13 +0,0 @@
|
||||
--- Makefile.orig Thu Nov 25 15:30:12 2004
|
||||
+++ Makefile Thu Nov 25 15:31:32 2004
|
||||
@@ -7,8 +7,8 @@
|
||||
#
|
||||
|
||||
FILE = memfetch
|
||||
-CFLAGS = -Wall -O9
|
||||
-CC = gcc
|
||||
+CFLAGS?= -Wall -O9
|
||||
+CC ?= gcc
|
||||
|
||||
all: $(FILE)
|
||||
|
@ -1,16 +1,7 @@
|
||||
Memfetch is a very simple utility that can be used to dump process memory of
|
||||
any userspace process running on the system without affecting its execution.
|
||||
Why bother? Well, quite often it is desirable to see what code and what data
|
||||
actually resides in memory under some pid (/proc entries are not always
|
||||
accurate). Debuggers like gdb are pretty good for examining small sections
|
||||
of code or memory, but are pretty much useless for massive comparison,
|
||||
sophisticated searches and such. It's good to be able to retrieve full
|
||||
memory image to run it thru grep, strings, your favorite viewer or any other
|
||||
tool. Quite obviously, I developed this code not because it's extremely
|
||||
difficult to do it on your own, but because it is a valuable shell utility
|
||||
for all kinds of deep hacking activities that simply saves you time.
|
||||
|
||||
Memfetch is a convenient screenshot grabber for ssh or screen sessions, by
|
||||
the way ;-)
|
||||
Memfetch is a simple utility to dump all memory of a running process, either
|
||||
immediately, or when a fault condition is discovered. It is an attractive
|
||||
alternative to the vastly inferior search capabilities of many debuggers and
|
||||
tracers -- and a convenient way to grab "screen shots" from many types of
|
||||
text-based interactive utilities, like ssh or screen sessions.
|
||||
|
||||
WWW: http://lcamtuf.coredump.cx/
|
||||
|
@ -1,5 +1,2 @@
|
||||
|
||||
Security Warning:
|
||||
This port requires that you mount procfs(5) filesystem in /proc.
|
||||
Please note that this can pose a security risk.
|
||||
|
||||
This port requires procfs(5) filesystem mounted under /proc.
|
||||
Please note that this can pose a security risk.
|
||||
|
Loading…
Reference in New Issue
Block a user