OK, thank you for your reply. Will do and will let you know. Reproducibility, should details of it be needed, is not an issue as the program I tried to debug is open-source and easily available.
Kind Regards Ariel Burbaickij On Sunday, June 26, 2022, Jon Turney <jon.tur...@dronecode.org.uk> wrote: > On 24/06/2022 15:13, Ariel Burbaickij wrote: > >> Hello mailing list, >> >> I was in the middle of deep debugging session when following happened: >> >> 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-11.2-1.x86_64/src/gdb-11.2/ >> gdb/infrun.c:2550: >> internal-error: void resume_1(gdb_signal): Assertion >> `pc_in_thread_step_range (pc, tp)' failed. >> A problem internal to GDB has been detected, >> further debugging may prove unreliable. >> ... >> application level programm (open source under GNU) from which I stepped >> into allocator crashes also somewhere near, so right now I am not sure >> what >> exactly gdb stumbles upon. GDB Core file is available. How do we proceed >> from here ? >> > > In the first place, please try the gdb 12.1 test package (available > through cygwin setup). > > If that doesn't improve matters, some details about how to (simply) > reproduce the problem would be nice. > > -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
