[AVAILMAN] V3 is out - VMS

This is a discussion on [AVAILMAN] V3 is out - VMS ; I see (after a 3.0 fieldtest phase) on http://www1.aclabs.com that AVAILMAN V3.0 is out now But http://www.openvms.digital.com/openv...ucts/availman/ still lists V2.6 as the current/newest version. What good is a products own homepage for when it's outdated? -- Peter "EPLAN" LANGSTOEGER Network ...

+ Reply to Thread
Results 1 to 13 of 13

Thread: [AVAILMAN] V3 is out

  1. [AVAILMAN] V3 is out

    I see (after a 3.0 fieldtest phase) on http://www1.aclabs.com that

    AVAILMAN V3.0 is out now

    But http://www.openvms.digital.com/openv...ucts/availman/ still lists
    V2.6 as the current/newest version.

    What good is a products own homepage for when it's outdated?

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  2. Re: V3 is out

    I see from the OpenVMS I64 OE - Q307 a link toHP Availability Manager
    for OpenVMS I64
    http://h30266.www3.hp.com/masterinde..._3_0_SSB.shtml
    and thence to the release notes
    http://h30266.www3.hp.com/masterinde...s_00111f98.txt

    I don't know if this DVD has shipped yet.



  3. Re: V3 is out

    Perhaps you can use the feedback form on
    http://h71000.www7.hp.com/openvms/pr...lman/news.html

    to ask?



  4. Re: V3 is out

    In article <1185202803.025569.20750@q75g2000hsh.googlegroups.c om>, IanMiller writes:
    >Perhaps you can use the feedback form on
    >http://h71000.www7.hp.com/openvms/pr...lman/news.html
    >
    >to ask?


    Yup. And I think, I found the answer myself. V3 is *still* in Beta (G3.0)...

    Sorry folks

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  5. Utility for finding memory leaks in C on VMS

    We have a program that must have a memory leak, but we can't find it.
    Any suggestions as to what we can use to find it? We can't recreate it
    in our test systems, it just shows up in our production system.

  6. Re: Utility for finding memory leaks in C on VMS

    In article <3DC4616854D6A84884BCB5FC545B35740161C30A@usplm203. amer.corp.eds.com>, "Williams, Arlen" writes:

    > We have a program that must have a memory leak, but we can't find it.
    > Any suggestions as to what we can use to find it?


    $ HELP DEBUG Heap_Analyzer

    > We can't recreate it
    > in our test systems, it just shows up in our production system.


    My first guess is that is due to an inadequate test suite.

    But run the Heap Analyzer, correct all defects, and you will likely
    find the leak goes away.

  7. Re: Utility for finding memory leaks in C on VMS

    In article <3DC4616854D6A84884BCB5FC545B35740161C30A@usplm203. amer.corp.eds.com>, "Williams, Arlen" writes:
    > We have a program that must have a memory leak, but we can't find it.
    > Any suggestions as to what we can use to find it? We can't recreate it
    > in our test systems, it just shows up in our production system.


    Not unusual. It probably means you have to run your tests longer,
    much longer.


  8. Re: Utility for finding memory leaks in C on VMS

    In article <0oE91Cj0Y50H@eisner.encompasserve.org>, koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes:
    > In article <3DC4616854D6A84884BCB5FC545B35740161C30A@usplm203. amer.corp.eds.com>, "Williams, Arlen" writes:
    >> We have a program that must have a memory leak, but we can't find it.
    >> Any suggestions as to what we can use to find it? We can't recreate it
    >> in our test systems, it just shows up in our production system.

    >
    > Not unusual. It probably means you have to run your tests longer,
    > much longer.


    Or with different data sets.

  9. Re: Utility for finding memory leaks in C on VMS

    Williams, Arlen wrote:
    > We have a program that must have a memory leak, but we can't find it.
    > Any suggestions as to what we can use to find it? We can't recreate it
    > in our test systems, it just shows up in our production system.


    There are tools for doing this on other platforms. Without changing
    platforms, your best bet is create wrappers for malloc() and maybe
    free() that attach some logging information to every allocation. Then
    you run your app for long enough to gobble up a significant amount of
    memory, dump it and see who allocated all that memory. Then you have
    the joyful task of figuring out who should have free()ed it.

    Some C programmers seem to feel that most memory usage should be
    dynamically allocated. A lot of the original thrust was due to
    computers that just didn't HAVE much memory and you had no choice but to
    recycle it. With virtual memory, this sort of thing is less necessary
    than it used to be.

    If you can build and run the code on a platform that has tools such as
    "Purify" (the name that comes to mind: I hope it's right) that's the way
    to go.


  10. Re: Utility for finding memory leaks in C on VMS

    In article <46DDD576.9090507@comcast.net>, "Richard B. Gilbert" writes:
    > Williams, Arlen wrote:
    >> We have a program that must have a memory leak, but we can't find it.
    >> Any suggestions as to what we can use to find it? We can't recreate it
    >> in our test systems, it just shows up in our production system.

    >
    > There are tools for doing this on other platforms. Without changing
    > platforms, your best bet is create wrappers for malloc() and maybe
    > free() that attach some logging information to every allocation.


    Why would one do that, when the Heap Analyzer already exists ?

  11. Re: Utility for finding memory leaks in C on VMS

    Larry Kilgallen wrote:
    > Why would one do that, when the Heap Analyzer already exists ?


    Does the heap analizer tell you which routine has allocated a block that
    wasn't deallocated later ?

    When you have an application with a mystery memory leak that doesn't
    happen all the time, going step by step in the debugger will take
    forever to find the memory leak.


    Wrapper routines allow you to add statements in the wrapper to log each
    call to some log file. And you can then log some separator betwene each
    transaction as well as some info about a transaction. And then check the
    log file to see if each transaction leaves some allocated block.

    (I had a counter, so that alloc would add 1 to it, and free would remove
    1 from it, so between transactions, I could easily see if all the
    structures allocated during a transactions were freed at end of
    transaction). You can then add more logging once you focus on where
    things might not get deallocated properly.

  12. Re: Utility for finding memory leaks in C on VMS

    On Tue, 04 Sep 2007 20:53:18 -0700, JF Mezei
    wrote:

    > Larry Kilgallen wrote:
    >> Why would one do that, when the Heap Analyzer already exists ?

    >
    > Does the heap analizer tell you which routine has allocated a block that
    > wasn't deallocated later ?
    >
    > When you have an application with a mystery memory leak that doesn't
    > happen all the time, going step by step in the debugger will take
    > forever to find the memory leak.
    >
    >
    > Wrapper routines allow you to add statements in the wrapper to log each
    > call to some log file. And you can then log some separator betwene each
    > transaction as well as some info about a transaction. And then check the
    > log file to see if each transaction leaves some allocated block.
    >
    > (I had a counter, so that alloc would add 1 to it, and free would remove
    > 1 from it, so between transactions, I could easily see if all the
    > structures allocated during a transactions were freed at end of
    > transaction). You can then add more logging once you focus on where
    > things might not get deallocated properly.


    That is what PL/I CONTROLLED storage does. You also can defined your own
    private
    heaps attach to specific programs using AREA. It is appalling to see the
    lack of
    progress in programming. The techiques we were using 40 years ago more
    sophisticated
    than what you guys are struggling with today. How stupid is that.



    --
    PL/I for OpenVMS
    www.kednos.com

  13. Re: Utility for finding memory leaks in C on VMS

    Williams, Arlen wrote:
    > We have a program that must have a memory leak, but we can't find it.
    > Any suggestions as to what we can use to find it? We can't recreate it
    > in our test systems, it just shows up in our production system.


    If the code is written in C, I have a wrapper for memory (de-)allocation
    routines to find leaks. You can find it at
    http://vms.pdv-systeme.de/users/martinv/memtrc.zip

    HTH,
    Martin
    --
    One OS to rule them all | Martin Vorlaender | OpenVMS rules!
    One OS to find them | work: mv@pdv-systeme.de
    One OS to bring them all | http://vms.pdv-systeme.de/users/martinv/
    And in the Darkness bind them.| home: martin.vorlaender@t-online.de

+ Reply to Thread