Bug 29513 - gdb itself crashes under Cygwin in the middle of debugging session on an application
Summary: gdb itself crashes under Cygwin in the middle of debugging session on an appl...
Status: UNCONFIRMED
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: 12.1
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-23 08:29 UTC by Ariel Burbaickij
Modified: 2022-11-02 18:10 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ariel Burbaickij 2022-08-23 08:29:33 UTC
I was debugging an application under Cygwin with gdb-12.1 when following happened to gdb itself:


1048          void* __place = _Raw_bytes_alloc(__alloc).allocate(__size);
(gdb) s
__gnu_cxx::new_allocator<char>::allocate (__n=85, this=<optimized out>)
    at /usr/src/debug/gcc-11.3.0-1/x86_64-pc-cygwin/libstdc++-v3/include/ext/new_allocator.h:103
103           allocate(size_type __n, const void* = static_cast<const void*>(0))
(gdb) s
__wrap__Znwm (sz=85) at /usr/src/debug/cygwin-3.3.5-1/winsup/cygwin/libstdcxx_wrapper.cc:55
55        return (*user_data->cxx_malloc->oper_new) (sz);
(gdb) s
/cygdrive/d/a/scallywag/gdb/gdb-12.1-1.x86_64/src/gdb-12.1/gdb/infrun.c:2553: internal-error: resume_1: Assertion `pc_in_thread_step_range (pc, tp)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
---------------------
/cygdrive/d/a/scallywag/gdb/gdb-12.1-1.x86_64/src/gdb-12.1/gdb/infrun.c:2553: internal-error: resume_1: Assertion `pc_in_thread_step_range (pc, tp)' failed.
Comment 1 Ariel Burbaickij 2022-08-23 08:31:47 UTC
it always crashed  on the same spot repeatedly in my debugging attempts on an application.