Re: GDB crashed with signal 11. Is it a bug in HP wdb? (502 Views)
Reply
Regular Advisor
blackwater
Posts: 129
Registered: ‎05-14-2009
Message 1 of 4 (529 Views)
Accepted Solution

GDB crashed with signal 11. Is it a bug in HP wdb?

[ Edited ]

bash-3.2$ GDB_SHLIB_PATH=`pwd`/core_data/some_modules:`pwd`/modules:`pwd`/core_data/packcore/modules gdb has_serverd core.has_serverd_1.14107
HP gdb 6.3 for HP Itanium (32 or 64 bit) and target HP-UX 11iv2 and 11iv3.
Copyright 1986 - 2011 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.3 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..

warning: core file may not match specified executable file.
Core was generated by `has_serverd_1'.
Program terminated with signal 11, Segmentation fault.
SEGV_ACCERR - Invalid Permissions for object
#0  0xc00000000cce64c0 in tc_new (size=<not available>) at linked_list.h:58

warning: Compilation directory is not absolute; could result in incorrect behavior.  Please report to HP.
58      linked_list.h: No such file or directory.
        in linked_list.h
(gdb) t 17620
[Switching to thread 17620 (system thread 9730317)]
#0  0xc000000002041650:0 in __lwp_sema_wait+0x30 ()
   from /import/home/hasg_tech/clm118765/modules/librt.so.1
(gdb) f 9
#9  0xc000000022053060:0 in selfcare::async_writers_thread::execute (warning: No unwind information found.
 Skipping this library /import/home/hasg_tech/clm118765/modules/libxalanMsg.so.


    this=0x6000000775837730) at critical_section.hpp:164
warning: Compilation directory is not absolute; could result in incorrect behavior.  Please report to HP.
164     critical_section.hpp: No such file or directory.
        in critical_section.hpp
(gdb) p *this
$1 = {<safethread> = {<thread> = {
      thread_info_mutex = {<noncopyable> = {<No data fields>}, m = {
          __m_short = {-24577, -1}, __m_int = -303382352, __m_int1 = {
            1610612742, -1631406976, -1610612737, -281239768},
          __m_ptr = 0x6000000746e36e10, __m_int2 = {1610612750, -724223744},
          __m_int3 = {1610612751, 1426304608, 1610612751, 1426304624},
          __m_short2 = {24576, 15}, __m_int4 = {1426304624, 5, 0, 0, 0},
          __m_int5 = {0, 0}}}, thread_info = {px = 0x6000000017add87a, pn = {
          pi_ = 0x2e80000000002b}}}, _aev = {<event> = {(0)  0x400000000025a950  gdb_crash_handler + 0xf0 at ../../../Src/gnu/gdb/main.c:2141 [/opt/langtools/bin/gdb]
(1)  0xe0000001267a7440  ---- Signal 11 (SIGSEGV) delivered ----
(2)  0x400000000028d150  check_typedef + 0x120 at ../../../Src/gnu/gdb/gdbtypes.c:1371 [/opt/langtools/bin/gdb]
(3)  0x40000000003b0b40  val_print + 0x80 at ../../../Src/gnu/gdb/valprint.c:140 [/opt/langtools/bin/gdb]
(4)  0x40000000003b8210  cp_print_value_fields + 0x8b0 at ../../../Src/gnu/gdb/cp-valprint.c:507 [/opt/langtools/bin/gdb]
(5)  0x40000000003bb1f0  cp_print_value + 0x840 at ../../../Src/gnu/gdb/cp-valprint.c:742 [/opt/langtools/bin/gdb]
(6)  0x40000000003b7b40  cp_print_value_fields + 0x1e0 at ../../../Src/gnu/gdb/cp-valprint.c:355 [/opt/langtools/bin/gdb]
(7)  0x40000000006dbe60  c_val_print + 0x1a0 at ../../../Src/gnu/gdb/c-valprint.c:348 [/opt/langtools/bin/gdb]
(8)  0x40000000003b0cc0  val_print + 0x200 at ../../../Src/gnu/gdb/valprint.c:164 [/opt/langtools/bin/gdb]
(9)  0x40000000003b8210  cp_print_value_fields + 0x8b0 at ../../../Src/gnu/gdb/cp-valprint.c:507 [/opt/langtools/bin/gdb]
(10) 0x40000000003bb1f0  cp_print_value + 0x840 at ../../../Src/gnu/gdb/cp-valprint.c:742 [/opt/langtools/bin/gdb]
(11) 0x40000000003b7b40  cp_print_value_fields + 0x1e0 at ../../../Src/gnu/gdb/cp-valprint.c:355 [/opt/langtools/bin/gdb]
(12) 0x40000000006dbe60  c_val_print + 0x1a0 at ../../../Src/gnu/gdb/c-valprint.c:348 [/opt/langtools/bin/gdb]
(13) 0x40000000003b0cc0  val_print + 0x200 at ../../../Src/gnu/gdb/valprint.c:164 [/opt/langtools/bin/gdb]
(14) 0x40000000006e20a0  c_value_print + 0x130 at ../../../Src/gnu/gdb/c-valprint.c:785 [/opt/langtools/bin/gdb]
(15) 0x40000000003b77e0  value_print + 0x120 at ../../../Src/gnu/gdb/valprint.c:218 [/opt/langtools/bin/gdb]
(16) 0x40000000003bbd90  print_formatted + 0x350 at ../../../Src/gnu/gdb/printcmd.c:492 [/opt/langtools/bin/gdb]
(17) 0x40000000005cbda0  print_command_1 + 0x290 at ../../../Src/gnu/gdb/printcmd.c:1444 [/opt/langtools/bin/gdb]
(18) 0x40000000005ce750  print_command + 0x30 at ../../../Src/gnu/gdb/printcmd.c:1467 [/opt/langtools/bin/gdb]
(19) 0x40000000003e74b0  execute_command + 0x670 at ../../../Src/gnu/gdb/top.c:1820 [/opt/langtools/bin/gdb]
(20) 0x4000000000630ca0  command_handler + 0x200 at ../../../Src/gnu/gdb/event-top.c:525 [/opt/langtools/bin/gdb]
(21) 0x40000000006301f0  command_line_handler + 0xe80 at ../../../Src/gnu/gdb/event-top.c:822 [/opt/langtools/bin/gdb]
(22) 0x40000000006315c0  rl_callback_read_char + 0x140 at ../../../Src/gnu/readline/callback.c:116 [/opt/langtools/bin/gdb]
(23) 0x4000000000631460  rl_callback_read_char_wrapper + 0x20 at ../../../Src/gnu/gdb/event-top.c:171 [/opt/langtools/bin/gdb]
(24) 0x400000000062c260  stdin_event_handler + 0x80 at ../../../Src/gnu/gdb/event-top.c:428 [/opt/langtools/bin/gdb]
(25) 0x400000000062c0e0  handle_file_event + 0x200 at ../../../Src/gnu/gdb/event-loop.c:758 [/opt/langtools/bin/gdb]
(26) 0x400000000062ac20  process_event + 0x1e0 at ../../../Src/gnu/gdb/event-loop.c:343 [/opt/langtools/bin/gdb]
(27) 0x400000000062aa10  gdb_do_one_event + 0x50 at ../../../Src/gnu/gdb/event-loop.c:395 [/opt/langtools/bin/gdb]
(28) 0x4000000000200fb0  catch_errors + 0x190 at ../../../Src/gnu/gdb/top.c:759 [/opt/langtools/bin/gdb]
(29) 0x400000000062a3a0  start_event_loop + 0x50 at ../../../Src/gnu/gdb/event-loop.c:438 [/opt/langtools/bin/gdb]
(30) 0x40000000005fbab0  cli_command_loop + 0x270 at ../../../Src/gnu/gdb/event-top.c:203 [/opt/langtools/bin/gdb]
(31) 0x400000000074c6b0  captured_command_loop + 0x70 at ../../../Src/gnu/gdb/main.c:259 [/opt/langtools/bin/gdb]
(32) 0x4000000000200fb0  catch_errors + 0x190 at ../../../Src/gnu/gdb/top.c:759 [/opt/langtools/bin/gdb]
(33) 0x4000000000258610  captured_main + 0x17c0 at ../../../Src/gnu/gdb/main.c:1601 [/opt/langtools/bin/gdb]
(34) 0x4000000000200fb0  catch_errors + 0x190 at ../../../Src/gnu/gdb/top.c:759 [/opt/langtools/bin/gdb]
(35) 0x4000000000200de0  main + 0x60 at ../../../Src/gnu/gdb/main.c:1614 [/opt/langtools/bin/gdb]
(36) 0xc00000000008ebc0  main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]

        erase_event = GDB crashed with signal 11! About to dump core into 'core' in the directory:
/import/home/hasg_tech/clm118765
Select one of the following options...
[N] No, do not dump core
[Y] Yes, dump core (default)
    NOTE: Make sure to rename any existing core file in this
          directory, as gdb's core will overwrite it.
[C] Continue execution (at your own risk)
>

Acclaimed Contributor
Dennis Handly
Posts: 25,054
Registered: ‎03-06-2006
Message 2 of 4 (518 Views)

Re: gdb crashed with signal 11. Is it a bug in HP wdb?

[ Edited ]

It depends.  Are you using aCC6 or g++ to compile?

In any case, please report the problem.

Regular Advisor
blackwater
Posts: 129
Registered: ‎05-14-2009
Message 3 of 4 (502 Views)

Re: GDB crashed with signal 11. Is it a bug in HP wdb?

[ Edited ]

> It depends.  Are you using aCC6 or g++ to compile?

I have been using g++.  HP wdb documentation clearly states: "WDB can be used to
debug code generated by the HP ANSI C, HP ANSI aC++ and HP Fortran compilers
as well as the GNU C and C++ compilers.". Why "It depends"?

 

 

 

 

Acclaimed Contributor
Dennis Handly
Posts: 25,054
Registered: ‎03-06-2006
Message 4 of 4 (488 Views)

Re: gdb crashed with signal 11. Is it a bug in HP wdb?

>Why "It depends"?

 

There may be slight differences in the debug info that isn't handled properly.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.