public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "orgads at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29294] [REG 11.2->12.1] Internal error when stepping into a function Date: Tue, 28 Jun 2022 17:42:45 +0000 [thread overview] Message-ID: <bug-29294-4717-KYWtRmR89f@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29294-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29294 --- Comment #2 from Orgad Shaneh <orgads at gmail dot com> --- This is the trace without debugging symbols: msvcrt!abort dump_core() internal_vproblem(internal_problem *, const char *, int, const char *, char *) internal_verror(const char *, int, const char *, char *) internal_error(const char *, int, const char *, ...) cp_print_class_member(unsigned const char *, type *, ui_file *, const char *) c_value_print_inner(value *, ui_file *, int, value_print_options const *) common_val_print(value *, ui_file *, int, value_print_options const *, language_defn const *) print_frame_arg(frame_print_options const&, frame_arg const *) print_frame_args(frame_print_options const&, symbol *, frame_info *, int, ui_file *) print_frame_info(frame_print_options const&, frame_info *, int, print_what, int, int) print_stack_frame(frame_info *, int, print_what, int) print_stop_event(ui_out *, bool) mi_on_normal_stop(bpstat *, int) normal_stop() fetch_inferior_event() check_async_event_handlers() gdb_do_one_event() captured_command_loop() gdb_main(captured_main_args *) I'm building now from master, will hopefully have more data. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-28 17:42 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-27 20:03 [Bug gdb/29294] New: " orgads at gmail dot com 2022-06-27 20:10 ` [Bug gdb/29294] " orgads at gmail dot com 2022-06-28 17:31 ` tromey at sourceware dot org 2022-06-28 17:42 ` orgads at gmail dot com [this message] 2022-06-28 19:22 ` orgads at gmail dot com 2022-06-28 19:54 ` orgads at gmail dot com 2022-06-30 8:53 ` orgads at gmail dot com 2022-06-30 9:14 ` orgads at gmail dot com 2022-06-30 12:27 ` orgads at gmail dot com 2022-06-30 12:35 ` vries at gcc dot gnu.org 2022-06-30 12:56 ` vries at gcc dot gnu.org 2022-06-30 13:19 ` vries at gcc dot gnu.org 2022-06-30 13:22 ` [Bug exp/29294] " vries at gcc dot gnu.org 2022-06-30 13:44 ` vries at gcc dot gnu.org 2022-06-30 13:45 ` orgads at gmail dot com 2022-06-30 13:54 ` vries at gcc dot gnu.org 2022-06-30 14:09 ` vries at gcc dot gnu.org 2022-06-30 15:00 ` vries at gcc dot gnu.org 2022-07-05 20:43 ` vries at gcc dot gnu.org
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-29294-4717-KYWtRmR89f@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).