In regard to: Re: [Networker] NetWorker 7.3.4 and Linux?, Preston de Guise...:
[root@earlgrey nw734]# nsrim -X
*** glibc detected *** nsrim: free(): invalid pointer: 0xbf921af0 ***
Clearly a bug in NetWorker. However, you can make glibc's memory
allocation more forgiving of bad behavior by setting the MALLOC_CHECK_
environment variable.
Try doing
MALLOC_CHECK_=1
export MALLOC_CHECK_
nsrim -X
You will still get warnings, but it may no longer crash.
I've found in relation to nsrmmd issues that doing this is VERY bad and
creates more problems than it solves.
Can you elaborate?
While it's a workaround until you get
a patch from EMC, trust me, you don't want to leave this setting in place
all the time.
True. Making malloc/free more forgiving of bad behavior is just a stopgap
that may or may not allow an application to (sort of) function. The real
fix is to fix the application.
I don't understand how EMC didn't detect this issue before 7.3.4 was
released.
[root@earlgrey ~]# MALLOC_CHECK_=1
[root@earlgrey ~]# export MALLOC_CHECK_
[root@earlgrey ~]# nsrim -X
malloc: using debugging hooks
*** glibc detected *** nsrim: free(): invalid pointer: 0xbfa6dc20 ***
It still printed the warning, which is expected (1 means warn but don't
purposely abort()). Did it still crash?
As I said, even setting it to 1 (or even 0, for no warning, no abort())
may not be enough to avoid the problem.
Tim
--
Tim Mooney Tim.Mooney AT ndsu DOT edu
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
