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 python/31296] New: [gdb/python, s390/m31] FAIL: gdb.python/py-disasm.exp: global_disassembler=GlobalPreInfoDisassembler: disassemble test (GDB internal error, virtual memory exhausted: can't allocate 2143909120 bytes)
Date: Fri, 26 Jan 2024 06:36:34 +0000	[thread overview]
Message-ID: <bug-31296-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31296
           Summary: [gdb/python, s390/m31] FAIL: gdb.python/py-disasm.exp:
                    global_disassembler=GlobalPreInfoDisassembler:
                    disassemble test (GDB internal error, virtual memory
                    exhausted: can't allocate 2143909120 bytes)
           Product: gdb
           Version: 13.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Created attachment 15333
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15333&action=edit
gdb.log

With a gdb-13.2 based package, on s390/m31 I run into:
...
(gdb) PASS: gdb.python/py-disasm.exp:
global_disassembler=GlobalPreInfoDisassembler: python
add_global_disassembler(GlobalPreInfoDisassembler)
disassemble test
Dump of assembler code for function test:
   0x00400538 <+0>:     st      %r11,44(%r15)
   0x0040053c <+4>:     lr      %r11,%r15
   0x0040053e <+6>:     nop     0
=> 0x00400542 <+10>:    ../../gdb/utils.c:718: internal-error: virtual memory
exhausted: can't allocate 2143909120 bytes.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
FAIL: gdb.python/py-disasm.exp: global_disassembler=GlobalPreInfoDisassembler:
disassemble test (GDB internal error)
Resyncing due to internal error.
0x4ffc53 gdb_internal_backtrace_1
        ../../gdb/bt-utils.c:122
0x4ffc53 _Z22gdb_internal_backtracev
        ../../gdb/bt-utils.c:168
0x91e7c9 internal_vproblem
        ../../gdb/utils.c:396
0x91eb17 _Z15internal_verrorPKciS0_P13__va_list_tag
        ../../gdb/utils.c:476
0xb0471d _Z18internal_error_locPKciS0_z
        ../../gdbsupport/errors.cc:58
0x91aec5 _Z14malloc_failurel
        ../../gdb/utils.c:718
0x4741c5 xmalloc
        ../../gdb/alloc.c:59
0x79adf1 disasmpy_info_read_memory
        ../../gdb/python/py-disasm.c:449
0x7cf6d7b5 ???
0x7cfaaa07 ???
0x7cfaaac1 ???
0x7cede329 ???
0x79b7ef gdb_PyObject_CallMethod<unsigned int, long long int>
        ../../gdb/python/python-internal.h:150
0x79b7ef _ZN18gdbpy_disassembler16read_memory_funcEyPhjP16disassemble_info
        ../../gdb/python/py-disasm.c:539
0x96dcb1 print_insn_s390
        ../../opcodes/s390-dis.c:337
0x79b257 disasmpy_builtin_disassemble
        ../../gdb/python/py-disasm.c:333
0x7cf92f1f ???
0x7cf92dfd ???
0x7cf983e9 ???
0x7cf71cd1 ???
0x7cf6d7b5 ???
0x7cf6ed39 ???
0x7cf6d7b5 ???
0x7cf05e55 ???
0x7cf6d7b5 ???
0x7cf92cc1 ???
0x7cf983e9 ???
0x7cf71cd1 ???
0x7cf6d7b5 ???
0x7cf6d9d1 ???
0x79bd6d _Z16gdbpy_print_insnP7gdbarchyP16disassemble_info
        ../../gdb/python/py-disasm.c:799
0x61386f _Z19ext_lang_print_insnP7gdbarchyP16disassemble_info
        ../../gdb/extension.c:940
0x588835 gdb_print_insn_1
        ../../gdb/disasm.c:1078
0x5895c1 _ZN16gdb_disassembler10print_insnEyPi
        ../../gdb/disasm.c:1101
0x589b59
_ZN29gdb_pretty_print_disassembler17pretty_print_insnEPK11disasm_insn10enum_flagsI20gdb_disassembly_flagE
        ../../gdb/disasm.c:445
0x58a203 dump_insns
        ../../gdb/disasm.c:542
0x58ab4b do_assembly_only
        ../../gdb/disasm.c:942
0x58ab4b
_Z15gdb_disassemblyP7gdbarchP6ui_out10enum_flagsI20gdb_disassembly_flagEiyy
        ../../gdb/disasm.c:1184
0x52a625 print_disassembly
        ../../gdb/cli/cli-cmds.c:1455
0x52f259 disassemble_command
        ../../gdb/cli/cli-cmds.c:1631
0x5326b9 _Z8cmd_funcP16cmd_list_elementPKci
        ../../gdb/cli/cli-decode.c:2543
0x8e5255 _Z15execute_commandPKci
        ../../gdb/top.c:690
0x60e117 _Z15command_handlerPKc
        ../../gdb/event-top.c:628
0x60f0d7 _Z20command_line_handlerOSt10unique_ptrIcN3gdb13xfree_deleterIcEEE
        ../../gdb/event-top.c:864
0x60d567 gdb_rl_callback_handler
        ../../gdb/event-top.c:256
0x961f5f rl_callback_read_char
        ../../../readline/readline/callback.c:290
0x60d797 gdb_rl_callback_read_char_wrapper_noexcept
        ../../gdb/event-top.c:192
0x60d989 gdb_rl_callback_read_char_wrapper
        ../../gdb/event-top.c:231
0x60d3c1 stdin_event_handler
        ../../gdb/event-top.c:553
0xb04fb9 gdb_wait_for_event
        ../../gdbsupport/event-loop.cc:694
0xb057e9 _Z16gdb_do_one_eventi
        ../../gdbsupport/event-loop.cc:264
0x6fbaab start_event_loop
        ../../gdb/main.c:411
0x6fbaab captured_command_loop
        ../../gdb/main.c:471
0x6fd223 captured_main
        ../../gdb/main.c:1330
0x6fd223 _Z8gdb_mainP18captured_main_args
        ../../gdb/main.c:1345
0x41cc1b main
        ../../gdb/gdb.c:32
...

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

                 reply	other threads:[~2024-01-26  6:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-31296-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).