Re: NOEMEM and SIGSEGV

From: Lars Bausch (lars.bausch_at_dotsch.de)
Date: 05/28/05

  • Next message: madhu: "gcc issue with HP-UX 11.23 PA RISC" 
    Date: Sat, 28 May 2005 18:07:04 +0200

    Hello Mike !

    Mike Stroyan wrote:
    >>I have compiled the boinc client and setiathome app for hpux.
    >>On the most systems both runs without problems.
    >>
    >>But one user have on two systems the problem, that he get a lot of
    >>ENOMEM, results in a SIGSEGV (I_NOEXIST).
    >
    >
    > The ENOMEM results are normal. They happen when a shared library
    > is referenced more than once. The mmap fails because the file is
    > already mapped. The dynamic loader sees that and carries on.
    On my systems, where the binary runs successfull, there are no ENOMEMs
    in the tusc output, so I thought, that the ENOMEM is the failure.

    Regards

    Lars

  • Next message: madhu: "gcc issue with HP-UX 11.23 PA RISC"

    Relevant Pages

    • Re: NOEMEM and SIGSEGV
      ... Mike Stroyan wrote: ... >>I have compiled the boinc client and setiathome app for hpux. ...
      (comp.sys.hp.hpux)
    • Re: NOEMEM and SIGSEGV
      ... > I have compiled the boinc client and setiathome app for hpux. ... The ENOMEM results are normal. ... from address -4 using a null pointer in r24. ...
      (comp.sys.hp.hpux)
    • NOEMEM and SIGSEGV
      ... I have compiled the boinc client and setiathome app for hpux. ... ENOMEM, results in a SIGSEGV. ...
      (comp.sys.hp.hpux)