public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30705] New: [gdb] UNRESOLVED: gdb.base/all-architectures-2.exp: tests: osabi=AIX: arch=bpf: endian=auto: disassemble 0x100,+4 (segfault)
Date: Mon, 31 Jul 2023 09:59:46 +0000	[thread overview]
Message-ID: <bug-30705-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30705

            Bug ID: 30705
           Summary: [gdb] UNRESOLVED: gdb.base/all-architectures-2.exp:
                    tests: osabi=AIX: arch=bpf: endian=auto: disassemble
                    0x100,+4 (segfault)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I'm running into:
...
ERROR: GDB process no longer exists
FAIL: gdb.base/all-architectures-2.exp: all passed
ERROR: GDB process no longer exists
FAIL: gdb.base/all-architectures-7.exp: all passed
...

In more detail:
...
(gdb) IPASS: gdb.base/all-architectures-2.exp: tests: osabi=AIX: arch=bpf:
endian=auto: print, float
disassemble 0x100,+4
Dump of assembler code from 0x100 to 0x104:

Fatal signal: Segmentation fault
----- Backtrace -----
0x59ef98 gdb_internal_backtrace_1
        /data/vries/gdb/src/gdb/bt-utils.c:122
0x59f03b _Z22gdb_internal_backtracev
        /data/vries/gdb/src/gdb/bt-utils.c:168
0x79029e handle_fatal_signal
        /data/vries/gdb/src/gdb/event-top.c:889
0x79040a handle_sigsegv
        /data/vries/gdb/src/gdb/event-top.c:962
0x7f9076c3f90f ???
       
/usr/src/debug/glibc-2.31-150300.52.2.x86_64/nptl/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0xefcdc4 print_insn_bpf
        /data/vries/gdb/src/opcodes/bpf-dis.c:152
0x4d0725 _Z18default_print_insnmP16disassemble_info
        /data/vries/gdb/src/gdb/arch-utils.c:1041
0x54f544 bpf_gdb_print_insn
        /data/vries/gdb/src/gdb/bpf-tdep.c:128
0x4d9af9 _Z18gdbarch_print_insnP7gdbarchmP16disassemble_info
        /data/vries/gdb/src/gdb/gdbarch.c:3329
0x69ed16 gdb_print_insn_1
        /data/vries/gdb/src/gdb/disasm.c:1099
0x69edde _ZN16gdb_disassembler10print_insnEmPi
        /data/vries/gdb/src/gdb/disasm.c:1116
0x69cd98
_ZN29gdb_pretty_print_disassembler17pretty_print_insnEPK11disasm_insn10enum_flagsI20gdb_disassembly_flagE
        /data/vries/gdb/src/gdb/disasm.c:446
0x69d26c dump_insns
        /data/vries/gdb/src/gdb/disasm.c:543
0x69e784 do_assembly_only
        /data/vries/gdb/src/gdb/disasm.c:957
0x69f1fc
_Z15gdb_disassemblyP7gdbarchP6ui_out10enum_flagsI20gdb_disassembly_flagEimm
        /data/vries/gdb/src/gdb/disasm.c:1199
0x5f0e77 print_disassembly
        /data/vries/gdb/src/gdb/cli/cli-cmds.c:1518
0x5f16ba disassemble_command
        /data/vries/gdb/src/gdb/cli/cli-cmds.c:1694
0x5f7b4e do_simple_func
        /data/vries/gdb/src/gdb/cli/cli-decode.c:95
0x5fcb62 _Z8cmd_funcP16cmd_list_elementPKci
        /data/vries/gdb/src/gdb/cli/cli-decode.c:2735
0xc5ee29 _Z15execute_commandPKci
        /data/vries/gdb/src/gdb/top.c:575
0x78fa57 _Z15command_handlerPKc
        /data/vries/gdb/src/gdb/event-top.c:552
0x78ff5f _Z20command_line_handlerOSt10unique_ptrIcN3gdb13xfree_deleterIcEEE
        /data/vries/gdb/src/gdb/event-top.c:788
0xc8b209 tui_command_line_handler
        /data/vries/gdb/src/gdb/tui/tui-interp.c:104
0x78f3ad gdb_rl_callback_handler
        /data/vries/gdb/src/gdb/event-top.c:259
0xd98279 rl_callback_read_char
        /data/vries/gdb/src/readline/readline/callback.c:290
0x78f215 gdb_rl_callback_read_char_wrapper_noexcept
        /data/vries/gdb/src/gdb/event-top.c:195
0x78f2b1 gdb_rl_callback_read_char_wrapper
        /data/vries/gdb/src/gdb/event-top.c:234
0xcb4743 stdin_event_handler
        /data/vries/gdb/src/gdb/ui.c:155
0x14a62ab handle_file_event
        /data/vries/gdb/src/gdbsupport/event-loop.cc:573
0x14a6841 gdb_wait_for_event
        /data/vries/gdb/src/gdbsupport/event-loop.cc:694
0x14a5707 _Z16gdb_do_one_eventi
        /data/vries/gdb/src/gdbsupport/event-loop.cc:264
0x919c46 start_event_loop
        /data/vries/gdb/src/gdb/main.c:412
0x919da0 captured_command_loop
        /data/vries/gdb/src/gdb/main.c:476
0x91b58c captured_main
        /data/vries/gdb/src/gdb/main.c:1320
0x91b626 _Z8gdb_mainP18captured_main_args
        /data/vries/gdb/src/gdb/main.c:1339
0x4195cd main
        /data/vries/gdb/src/gdb/gdb.c:32
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible.  GDB will now terminate.

This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

ERROR: GDB process no longer exists
GDB process exited with wait status 25141 exp9 0 0 CHILDKILLED SIGSEGV
{segmentation violation}
UNRESOLVED: gdb.base/all-architectures-2.exp: tests: osabi=AIX: arch=bpf:
endian=auto: disassemble 0x100,+4
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-07-31  9:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  9:59 vries at gcc dot gnu.org [this message]
2023-07-31 10:01 ` [Bug gdb/30705] " vries at gcc dot gnu.org
2023-07-31 10:07 ` vries at gcc dot gnu.org
2023-07-31 10:09 ` vries at gcc dot gnu.org
2023-07-31 10:14 ` [Bug tdep/30705] " vries at gcc dot gnu.org
2023-07-31 10:45 ` jose.marchesi at oracle dot com
2023-07-31 11:03 ` vries at gcc dot gnu.org
2023-07-31 11:16 ` vries at gcc dot gnu.org
2023-07-31 13:03 ` mark at klomp dot org
2023-07-31 13:46 ` cvs-commit at gcc dot gnu.org
2023-07-31 14:15 ` vries at gcc dot gnu.org
2023-07-31 21:04 ` vries at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30705-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).