In , on 10/10/2013
at 04:42 PM, Clifford McNeill said:
>My preferred term is 'programming error'
You'd change your mind pretty quickly if people started reporting
errors as "programming error" instead of giving the details.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO positi
In <004301cec5ff$433d3460$c9b79d20$@mcn.org>, on 10/10/2013
at 02:25 PM, Charles Mills said:
> Except for the fact that "memory leak" is an established term
>that most folks agree on and recognize, I would
>support the terminology "failure to free" error.
How would you describe a GETMAIN 0f
In <5256fc8d.7050...@actionsoftware.com>, on 10/10/2013
at 03:14 PM, Gord Tomlin said:
>Most readers would infer that "memory error" indicated that the
>(hardware) memory had a fault,
I'd interpret it as any of half a dozen errors[1], none of which are
storage leak. I would only interpret it
Well then...they just don't know how to use the tools they have. Lovely.
On Thu, Oct 10, 2013 at 9:58 PM, David Crayford wrote:
> On 11/10/2013 5:47 AM, Charles Mills wrote:
>
>> FWIW, MS Visual Studio 2010, which I use for editing and alpha testing,
>> has
>> excellent memory leak diagnosis fac
on List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of zMan
Sent: Thursday, October 10, 2013 2:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How diagnose potential memory leaks with LE?
Ditto. I think they like 'leak' because they have no decent tools (in too
many cases, not all!) to diagn
In <007a01cec5e3$c3ffeaa0$4bffbfe0$@mxg.com>, on 10/10/2013
at 01:08 PM, Barry Merrill said:
>Is there really a reason to call a z/OS MEMORY ERROR a LEAK???
Yes.
>It's an ERROR.
Yes, but if you're diagnosing an error you want to know the details.
--
Shmuel (Seymour J.) Metz, SysPro
Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Bernd Oppolzer
Sent: Thursday, October 10, 2013 10:34 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How diagnose potential memory leaks with LE?
To diagnose memory leaks, I use an alternate h
derstand the other report I am content with it, but I will keep
this in mind.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Bernd Oppolzer
Sent: Thursday, October 10, 2013 10:34 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re:
ecent tools" is not much of an excuse.
>
> Charles
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of zMan
> Sent: Thursday, October 10, 2013 2:33 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Ho
Finding that Charles agrees with me is more than a little
disconcerting, but I console myself by reflecting that it is very
unlikely to happen again during 2013 and probably not even in 2014.
Taken seriously, as of course it should/need not be, Cliff's
suggestion is too generic. 'Memory leak' is
on List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of zMan
Sent: Thursday, October 10, 2013 2:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How diagnose potential memory leaks with LE?
Ditto. I think they like 'leak' because they have no decent tools (in too
many cases, not all!) to d
My preferred term is 'programming error'
Cliff McNeill
> Date: Thu, 10 Oct 2013 17:33:04 -0400
> From: zedgarhoo...@gmail.com
> Subject: Re: How diagnose potential memory leaks with LE?
> To: IBM-MAIN@LISTSERV.UA.EDU
>
> Ditto. I think they like 'leak&#
n
> established term that most folks agree on and recognize, I would support
> the
> terminology "failure to free" error.
>
> Charles
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of John Gilmore
> Se
rame Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of John Gilmore
Sent: Thursday, October 10, 2013 11:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How diagnose potential memory leaks with LE?
Barry Merrill wrote:
Is there really a reason to call a z/OS MEMORY ERROR a LEAK???
BTW: we had a weird but not uncommon situation just in the last few days,
where a memory leak of only 32 bytes (allocated some 500 times) lead to
a short-on-storage termination of an address space of 512 MB.
This was due to the following allocation pattern:
there were some large areas allocated
On 2013-10-10 14:08, Barry Merrill wrote:
Is there really a reason to call a z/OS MEMORY ERROR a LEAK???
It's an ERROR. I know the Open Systems guys love to hide behind
words that make it NOT seem to be their error, but why us???
Barry
Another term I recall being used in the mainframe environ
t;To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: How diagnose potential memory leaks with LE?
>
>To diagnose memory leaks, I use an alternate heap manager called the "memory
>check heap manager". It keeps a statistic of all the allocated heap areas and
>prints a list of the unmatc
Barry Merrill wrote:
Is there really a reason to call a z/OS MEMORY ERROR a LEAK??? It's
an ERROR. I know the Open Systems guys love to hide behind words that
make it NOT seem to be their error, but why us???
and I strongly agree that the use of euphemisms for what are in fact
errors is undes
U] On Behalf
Of Bernd Oppolzer
Sent: Thursday, October 10, 2013 12:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How diagnose potential memory leaks with LE?
To diagnose memory leaks, I use an alternate heap manager called the "memory
check heap manager". It keeps a statistic of all the
Two additional hints:
the output goes to CEEMSGS, and:
this is not meant for production work, of course,
because the use of CEL4MCHK makes your application really slow;
it's only for diagnosing memory leak problems.
Kind regards
Bernd
Am 10.10.2013 19:34, schrieb Bernd Oppolzer:
To diagnos
To diagnose memory leaks, I use an alternate heap manager
called the "memory check heap manager". It keeps a statistic of all the
allocated heap areas and prints a list of the unmatched allocates at the
end
of the process. This proved to be very helpful in our environment to
find memory leaks
in
e = memory
leak.)
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Charles Mills
Sent: Wednesday, October 09, 2013 9:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: How diagnose potential memory leaks with LE?
I'm trying to see if a
Hi
I'm afraid the "new" operator has a "delete"at termination, so maybe
with "malloc" you will see the
storage leak.
On 10.10.2013 06:51, Charles Mills wrote:
I'm trying to see if a (batch, conventional z/OS, C++, 31-bit, V1R13)
program has memory leaks. After reading "Diagnosing storage
I'm trying to see if a (batch, conventional z/OS, C++, 31-bit, V1R13)
program has memory leaks. After reading "Diagnosing storage leak problems"
in the LE debugging guide, I run the program with
//CEEOPTS DD *
HEAPCHK(ON,1,0,10,10,1024,0)
/*
I get the foll
24 matches
Mail list logo
