<?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: pstack causes a coredump in getexecpath (on a bogus free) in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6139863#M496014</link>
    <description>&lt;P&gt;&amp;gt;There is a call to free at getexecpath.c:211 and it results in a coredump.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You should have left the free line in the stacktrace.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;gt;Is it possible that some kind of b&lt;SPAN&gt;uffer overflow happens in this line: getexecpath.c:211 inside pstack?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;No, it's worst that that.&amp;nbsp; :-(&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please contact Support and file a bug report.&amp;nbsp; You can have them contact me for details.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 19 Jul 2013 06:29:51 GMT</pubDate>
    <dc:creator>Dennis Handly</dc:creator>
    <dc:date>2013-07-19T06:29:51Z</dc:date>
    <item>
      <title>pstack causes a coredump in getexecpath ().</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6139017#M496013</link>
      <description>&lt;P&gt;A coredump of pstack is being analyzed by our team:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;#7  0x4000000000023da0:0 in getexecpath () at getexecpath.c:211
#8  0x4000000000022230:0 in pstack () at pstack.c:952
#9  0x40000000000216d0:0 in main () at pstack.c:1401&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is a call to free() at getexecpath.c:211 and it results in a coredump.&amp;nbsp; Is it possible that some kind of b&lt;SPAN&gt;uffer overflow happens in this line: getexecpath.c:211 inside pstack?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jul 2013 12:24:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6139017#M496013</guid>
      <dc:creator>blackwater</dc:creator>
      <dc:date>2013-07-18T12:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: pstack causes a coredump in getexecpath (on a bogus free)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6139863#M496014</link>
      <description>&lt;P&gt;&amp;gt;There is a call to free at getexecpath.c:211 and it results in a coredump.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You should have left the free line in the stacktrace.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;gt;Is it possible that some kind of b&lt;SPAN&gt;uffer overflow happens in this line: getexecpath.c:211 inside pstack?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;No, it's worst that that.&amp;nbsp; :-(&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please contact Support and file a bug report.&amp;nbsp; You can have them contact me for details.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2013 06:29:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6139863#M496014</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2013-07-19T06:29:51Z</dc:date>
    </item>
    <item>
      <title>Re: pstack causes a coredump in getexecpath (on a bogus free)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6140327#M496015</link>
      <description>&lt;P&gt;It seems that I managed to find a problem in HP pstack with HP gdb.&lt;/P&gt;&lt;P&gt;So I run "gdb pstack" and then set "set heap-check on". Then I do "run &amp;lt;PID&amp;gt;". And after that I get sometimes RTC_BAD_FREE. It means that pstack calls free and passes it an unallocated or already freed object!&lt;/P&gt;&lt;P&gt;As one can see from "info shared" below I use only HP libraries and HP utilities:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;(gdb) show heap-check
Thread debugging commands is "on".
Current heap check settings are :
        Check leaks      : on
        Check bounds     : on
        Check free()     : on
        Check string     : off
        Scrambling       : off
        Frame count      : 12
        Min-leak-size    : 0
        Min-heap-size    : 0
        Block-size       : 0
        Header-size      : 16
        Footer-size      : 1
        Seed-value       : 5
        Random-range     : 100
        Null-check       : -1
        Null-check-size  : -1
        Heap-size        : 0
        Heap Interval    : 0
        Repeat Count     : 100
        High-mem Count   : 0
        Watch Address    : 0x00000000
        retain-freed-blocks : off
(gdb) r 1772
Starting program: /usr/ccs/bin/pstack 1772
warning: Attempt to free unallocated or already freed object at 0x9fffffffffffda20
__rtc_event (ecode=RTC_BAD_FREE, pointer=0x9fffffffffffda20, pclist=0x0,
    size=0) at ../../../Src/gnu/gdb/infrtc.c:2145
2145    ../../../Src/gnu/gdb/infrtc.c: No such file or directory.
        in ../../../Src/gnu/gdb/infrtc.c
(gdb) bt
#0  __rtc_event (ecode=RTC_BAD_FREE, pointer=0x9fffffffffffda20, pclist=0x0,
    size=0) at ../../../Src/gnu/gdb/infrtc.c:2145
#1  0x9fffffffff6022b0:0 in rtc_record_free (pointer=&amp;lt;not available&amp;gt;,
    free_the_block=&amp;lt;not available&amp;gt;, is_realloc=&amp;lt;not available&amp;gt;)
    at ../../../Src/gnu/gdb/infrtc.c:3968
#2  0x9fffffffff604d20:0 in free (p=0x9fffffffffffda20)
    at ../../../Src/gnu/gdb/infrtc.c:4484
#3  0x4000000000023da0:0 in getexecpath () at getexecpath.c:211
#4  0x4000000000022230:0 in pstack () at pstack.c:952
#5  0x40000000000216d0:0 in main () at pstack.c:1401
(gdb) info sharedlibrary
Shared Object Libraries
        tstart              tend              dstart              dend               gp
/usr/lib/hpux64/dld.so
0x9fffffffff640000 0x9fffffffff6f95f0 0x9fffffffff63a000 0x9fffffffff63fa38 0x9fffffffff63cf30
/opt/langtools/lib/hpux64/librtc.so
0x9fffffffff5c8000 0x9fffffffff632690 0x9fffffffff4e2000 0x9fffffffff5c7958 0x9fffffffff554968
/usr/lib/hpux64/libunwind.so.1
0x9fffffffff478000 0x9fffffffff4df410 0x9fffffffff6fe000 0x9fffffffff6fed68 0x9fffffffff6fe9e0
/usr/lib/hpux64/libuca.so.1
0x9fffffffff46c000 0x9fffffffff474020 0x9fffffffff633000 0x9fffffffff633150 0x9fffffffff633128
/usr/lib/hpux64/libc.so.1
0x9fffffffff100000 0x9fffffffff3b9ba0 0x9fffffffff453000 0x9fffffffff4692b8 0x9fffffffff45ce98
/usr/lib/hpux64/libcl.so.1
0x9fffffffff4e1000 0x9fffffffff4e150c 0x9fffffffff4e0000 0x9fffffffff4e0018 0x9fffffffff4e0010
/usr/lib/hpux64/libCsup.so.1
0x9fffffffff3ec000 0x9fffffffff44af80 0x9fffffffff3e4000 0x9fffffffff3ea3d8 0x9fffffffff3e96a8
/usr/lib/hpux64/libdl.so.1
0x9fffffffff3dc000 0x9fffffffff3e03b0 0x9fffffffff477000 0x9fffffffff4774f0 0x9fffffffff4770e8
/usr/lib/hpux64/libIO77.so.1
0x9ffffffffef24000 0x9fffffffff0ff2f0 0x9fffffffff3c2000 0x9fffffffff3db978 0x9fffffffff3ce738
Total of 9 shared libraries.&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2013 12:14:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6140327#M496015</guid>
      <dc:creator>blackwater</dc:creator>
      <dc:date>2013-07-19T12:14:13Z</dc:date>
    </item>
    <item>
      <title>Re: pstack causes a coredump in getexecpath (on a bogus free)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6140343#M496016</link>
      <description>&lt;P&gt;Just to clarify. At first I ran pstack with TCMalloc. TCMalloc::free() coredumps in case it gets a pointer that has not been allocated before. HP libc allocator and HP MallocNG allocator do not cause a coredump with pstack. Nevertheless when I run HP pstack under HP gdb with "set heap-check on " I get RTC_BAD_FREE. So there is undefined behavior in HP pstack.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2013 06:19:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6140343#M496016</guid>
      <dc:creator>blackwater</dc:creator>
      <dc:date>2013-07-22T06:19:40Z</dc:date>
    </item>
    <item>
      <title>Re: pstack causes a coredump in getexecpath (on a bogus free)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6140937#M496017</link>
      <description>&lt;P&gt;&amp;gt;So there is an undefined behavior in HP pstack.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's correct.&amp;nbsp; :-(&amp;nbsp; There is a bogus call to free.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2013 02:44:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6140937#M496017</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2013-07-26T02:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: pstack causes a coredump in getexecpath (on a bogus free)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6147927#M496018</link>
      <description>&lt;P&gt;Reproduced this issue in pstack. As Dennis sugested&amp;nbsp;&lt;SPAN&gt;Please contact Support and file a bug report.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jul 2013 16:29:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pstack-causes-a-coredump-in-getexecpath/m-p/6147927#M496018</guid>
      <dc:creator>ShridharJoshi</dc:creator>
      <dc:date>2013-07-25T16:29:33Z</dc:date>
    </item>
  </channel>
</rss>

