account needed for gdb bug report

Ariel Burbaickij ariel.burbaickij@gmail.com
Tue Aug 23 07:42:27 GMT 2022


Hello sourceware overseers,

I encountered following gdb internal bug/crash:

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.


while debugging application under Cygwin. Cygwin's gdb maintainer Jon
Turney currently does not have any time to look into it and asked me to
open bug report with you directly for which I need an account which cannot
be created in self-service mode. Could you, please, open an account for me
?

Kind Regards
Ariel Burbaickij


More information about the Overseers mailing list