<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SIGSEGV and kernel parameters in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635807#M850577</link>
    <description>Here are the lines surrounding it. As you can see it is reading from a socket and completes the read, but then bails. Will install GDB and check the core file.&lt;BR /&gt;&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "0 ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "1 ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "9 ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "\n", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662]   Received signal 11, SIGSEGV, in user mode, [SIG_DFL], partial siginfo&lt;BR /&gt;[extprocPLSEx][7662]     Siginfo: si_code: I_NONEXIST, faulting address: 0x3c2b4fd8, si_errno: 0&lt;BR /&gt;[extprocPLSEx][7662]     PC: 0xc019c5b7, instruction: 0x4b570030&lt;BR /&gt;[extprocPLSEx][7662] exit(11) [implicit] ..................................................................... WIFSIGNALED(SIGSEGV)|&lt;BR /&gt;WCOREDUMP&lt;BR /&gt;[/orarpc/bin/][6940] select(2048, 0x7b0445c8, NULL, NULL, NULL) .............................................. = 1&lt;BR /&gt;[/orarpc/bin/][6940] gettimeofday(0x7b0444f0, NULL) .......................................................... = 0&lt;BR /&gt;[/orarpc/bin/][6940] gettimeofday(0x7b04a7f0, NULL) .......................................................... = 0&lt;BR /&gt;[/orarpc/bin/][6940] getsockname(7, 0x7b04ab2c, 0x7b04ab20) .................................................. = 0&lt;BR /&gt;[/orarpc/bin/][6940] accept(7, 0x7b04ab00, 0x7b04aafc) ....................................................... = 12&lt;BR /&gt;[/orarpc/bin/][6940] fcntl(12, F_SETFD, 1) ................................................................... = 0&lt;BR /&gt;[/orarpc/bin/][6940] ioctl(12, FIONBIO, 0x7b04a5f8) .......................................................... = 0&lt;BR /&gt;[/orarpc/bin/][6940] sigaction(SIGPIPE, 0x7b04a5f0, 0x7b04a618) .............................................. = 0&lt;BR /&gt;[/orarpc/bin/][6940] select(2048, 0x7b0445c8, 0x7b0446c8, NULL, NULL) ........................................ = 1&lt;BR /&gt;[/orarpc/bin/][6940] gettimeofday(0x7b0444f0, NULL) .......................................................... = 0</description>
    <pubDate>Thu, 27 Dec 2001 17:10:30 GMT</pubDate>
    <dc:creator>Phil Daws_2</dc:creator>
    <dc:date>2001-12-27T17:10:30Z</dc:date>
    <item>
      <title>SIGSEGV and kernel parameters</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635801#M850571</link>
      <description>Xmas Greetings all ...&lt;BR /&gt;&lt;BR /&gt;I have a problem where we are receiving a Segmentation Violation. I believe this is a problem due to our kernel parameters. We are running HPUX V11.11 on a N4000x4way with 8192MB RAM. Our current parameters are :&lt;BR /&gt;&lt;BR /&gt;maxdsiz_64bit   0xc0000000&lt;BR /&gt;maxtsiz_64bit   0x100000000&lt;BR /&gt;maxssiz_64bit   0x10000000&lt;BR /&gt;maxdsiz         0xc0000000&lt;BR /&gt;maxssiz         0x04fb3000&lt;BR /&gt;maxtsiz         0x40000000&lt;BR /&gt;&lt;BR /&gt;What would you recomend we up these too?&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;Phil</description>
      <pubDate>Thu, 27 Dec 2001 10:30:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635801#M850571</guid>
      <dc:creator>Phil Daws_2</dc:creator>
      <dc:date>2001-12-27T10:30:33Z</dc:date>
    </item>
    <item>
      <title>Re: SIGSEGV and kernel parameters</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635802#M850572</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;first in is impotentd that you will know how was your system install 32 bit or 64 bit .&lt;BR /&gt;&lt;BR /&gt;you can see it with the command : &lt;BR /&gt;getconf KERNEL_BITS&lt;BR /&gt;&lt;BR /&gt;i think that you are working with 64 bit .&lt;BR /&gt;&lt;BR /&gt;my advise it to change this param to there max. size .&lt;BR /&gt;&lt;BR /&gt;see this link for details on the params and what is the max size of this params ,&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com//hpux/onlinedocs/os/KCparams.OverviewAll.html" target="_blank"&gt;http://docs.hp.com//hpux/onlinedocs/os/KCparams.OverviewAll.html&lt;/A&gt;</description>
      <pubDate>Thu, 27 Dec 2001 11:46:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635802#M850572</guid>
      <dc:creator>eran maor</dc:creator>
      <dc:date>2001-12-27T11:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: SIGSEGV and kernel parameters</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635803#M850573</link>
      <description>A lot depends on the programs you are running. These are limits to prevent runaway programs from consuming too much memory. If your program is a 32-bit program, then it can't grow much beyond 940 megs of RAM without paying special attention to how the program is mapped into memory. There are separate rules for shared memory, and limits for stack are different for 32 versus 64 bit programs.  &lt;BR /&gt;&lt;BR /&gt;The N-class computer only runs a 64 bit kernel so there are no practical limits on RAM, but you need to look at the memory and process management papers in /usr/share/doc.</description>
      <pubDate>Thu, 27 Dec 2001 14:15:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635803#M850573</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2001-12-27T14:15:34Z</dc:date>
    </item>
    <item>
      <title>Re: SIGSEGV and kernel parameters</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635804#M850574</link>
      <description>Okay. But is there a formula for calculating the requirements or is it a figure up in the air and a best guestimate?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Phil</description>
      <pubDate>Thu, 27 Dec 2001 14:27:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635804#M850574</guid>
      <dc:creator>Phil Daws_2</dc:creator>
      <dc:date>2001-12-27T14:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: SIGSEGV and kernel parameters</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635805#M850575</link>
      <description>Here is a dump from TUSC when it fails :&lt;BR /&gt;&lt;BR /&gt;[extprocPLSEx][7662]   Received signal 11, SIGSEGV, in user mode, [SIG_DFL], partial siginfo&lt;BR /&gt;[extprocPLSEx][7662]     Siginfo: si_code: I_NONEXIST, faulting address: 0x3c2b4fd8, si_errno: 0&lt;BR /&gt;[extprocPLSEx][7662]     PC: 0xc019c5b7, instruction: 0x4b570030&lt;BR /&gt;&lt;BR /&gt;Scratching head now :)</description>
      <pubDate>Thu, 27 Dec 2001 16:42:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635805#M850575</guid>
      <dc:creator>Phil Daws_2</dc:creator>
      <dc:date>2001-12-27T16:42:33Z</dc:date>
    </item>
    <item>
      <title>Re: SIGSEGV and kernel parameters</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635806#M850576</link>
      <description>Phil,&lt;BR /&gt;&lt;BR /&gt;As Bill stated, it depends on what applications you are running.  I personally always set the maxdsiz parameter to the maximum on production systems because I have scripts that monitor the memory usage of processes and alert me when a certain threshold is reached.  I can then make a decision on whether it is normal or there is a memory leak and I need to shutdown the application.&lt;BR /&gt;&lt;BR /&gt;If you're getting a SIGSEGV it may or may not be related to these parameters, it could simply be a bug the program.  A couple of questions:&lt;BR /&gt;&lt;BR /&gt;- how big is the resulting corefile?  If the size of the core is equal to maxdsiz then thats likely to be your problem.  If its less than maxdsiz then your problem is elsewhere.&lt;BR /&gt;&lt;BR /&gt;- what are the lines immediately before the SIGSEGV line in your tusc trace?  Do any system calls return errno's?  I would expect an ENOMEM if you hit maxdsiz.  No errors in the tusc trace indicates that the program has simply tried to access memory illegally, and you won't get any more info from tusc on this.&lt;BR /&gt;&lt;BR /&gt;- do you have access to the source code?  If so, run the core file through a debugger like wdb or gdb and you can get a stack trace.  If not, send the core back to the vendor or application developers, along with any other relevant information.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Steve</description>
      <pubDate>Thu, 27 Dec 2001 16:54:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635806#M850576</guid>
      <dc:creator>Steven Gillard_2</dc:creator>
      <dc:date>2001-12-27T16:54:46Z</dc:date>
    </item>
    <item>
      <title>Re: SIGSEGV and kernel parameters</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635807#M850577</link>
      <description>Here are the lines surrounding it. As you can see it is reading from a socket and completes the read, but then bails. Will install GDB and check the core file.&lt;BR /&gt;&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "0 ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "1 ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "9 ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662] recv(6, "\n", 1, 0) ..................................................................... = 1&lt;BR /&gt;[extprocPLSEx][7662]   Received signal 11, SIGSEGV, in user mode, [SIG_DFL], partial siginfo&lt;BR /&gt;[extprocPLSEx][7662]     Siginfo: si_code: I_NONEXIST, faulting address: 0x3c2b4fd8, si_errno: 0&lt;BR /&gt;[extprocPLSEx][7662]     PC: 0xc019c5b7, instruction: 0x4b570030&lt;BR /&gt;[extprocPLSEx][7662] exit(11) [implicit] ..................................................................... WIFSIGNALED(SIGSEGV)|&lt;BR /&gt;WCOREDUMP&lt;BR /&gt;[/orarpc/bin/][6940] select(2048, 0x7b0445c8, NULL, NULL, NULL) .............................................. = 1&lt;BR /&gt;[/orarpc/bin/][6940] gettimeofday(0x7b0444f0, NULL) .......................................................... = 0&lt;BR /&gt;[/orarpc/bin/][6940] gettimeofday(0x7b04a7f0, NULL) .......................................................... = 0&lt;BR /&gt;[/orarpc/bin/][6940] getsockname(7, 0x7b04ab2c, 0x7b04ab20) .................................................. = 0&lt;BR /&gt;[/orarpc/bin/][6940] accept(7, 0x7b04ab00, 0x7b04aafc) ....................................................... = 12&lt;BR /&gt;[/orarpc/bin/][6940] fcntl(12, F_SETFD, 1) ................................................................... = 0&lt;BR /&gt;[/orarpc/bin/][6940] ioctl(12, FIONBIO, 0x7b04a5f8) .......................................................... = 0&lt;BR /&gt;[/orarpc/bin/][6940] sigaction(SIGPIPE, 0x7b04a5f0, 0x7b04a618) .............................................. = 0&lt;BR /&gt;[/orarpc/bin/][6940] select(2048, 0x7b0445c8, 0x7b0446c8, NULL, NULL) ........................................ = 1&lt;BR /&gt;[/orarpc/bin/][6940] gettimeofday(0x7b0444f0, NULL) .......................................................... = 0</description>
      <pubDate>Thu, 27 Dec 2001 17:10:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sigsegv-and-kernel-parameters/m-p/2635807#M850577</guid>
      <dc:creator>Phil Daws_2</dc:creator>
      <dc:date>2001-12-27T17:10:30Z</dc:date>
    </item>
  </channel>
</rss>

