public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "georgebateman16 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29871] New: "p tail.y ++ (diff.y / 2)" command causes crash Date: Sat, 10 Dec 2022 21:03:15 +0000 [thread overview] Message-ID: <bug-29871-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29871 Bug ID: 29871 Summary: "p tail.y ++ (diff.y / 2)" command causes crash Product: gdb Version: 12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: georgebateman16 at gmail dot com Target Milestone: --- Created attachment 14491 --> https://sourceware.org/bugzilla/attachment.cgi?id=14491&action=edit GDB session resulting in crash While debugging a C application I entered the command "p tail.y ++ (diff.y / 2)". (This was a typo; I intended to write "+=".) This caused GDB to crash and output the attached backtrace, starting with: /build/gdb-YpKTRx/gdb-12.1/gdb/gdbtypes.c:3914: internal-error: is_nocall_function: Assertion `type->code () == TYPE_CODE_FUNC || type->code () == TYPE_CODE_METHOD' failed. The tail and diff objects are instances of the below struct, if that is relevant. typedef struct { int x; int y; } coord; System information (also in the attachment): GCC VERSION Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 12.2.0-9' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-12 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-12-lH3g9c/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-lH3g9c/gcc-12-12.2.0/debian/tmp-gcn/usr --enable-offload-defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.2.0 (Debian 12.2.0-9) Linux gbat-hp-linux 6.0.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.8-1 (2022-11-11) x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-12-10 21:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-10 21:03 georgebateman16 at gmail dot com [this message] 2022-12-10 22:30 ` [Bug gdb/29871] " simark at simark dot ca 2022-12-11 19:54 ` tromey at sourceware dot org 2022-12-13 5:03 ` cvs-commit at gcc dot gnu.org 2022-12-13 5:04 ` tromey at sourceware dot org 2023-03-20 14:45 ` alexandr.miloslavskiy at syntevo dot com
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-29871-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: linkBe 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).