From: Ariel Burbaickij <ariel.burbaickij@gmail.com>
To: overseers@sourceware.org
Subject: account needed for gdb bug report
Date: Tue, 23 Aug 2022 09:42:27 +0200 [thread overview]
Message-ID: <CANeJNHqgC29i0GAnZ+O-cRX+sibjnJJ3GNPQhRHVzRFVyYEahg@mail.gmail.com> (raw)
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
next reply other threads:[~2022-08-23 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:42 Ariel Burbaickij [this message]
2022-08-23 7:54 ` Mark Wielaard
2022-08-23 7:58 ` Ariel Burbaickij
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=CANeJNHqgC29i0GAnZ+O-cRX+sibjnJJ3GNPQhRHVzRFVyYEahg@mail.gmail.com \
--to=ariel.burbaickij@gmail.com \
--cc=overseers@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).