public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "libin.dang at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29742] [ARMv7] [gdbserver] maybe_hw_step: Assertion `has_single_step_breakpoints (thread)' failed. Date: Fri, 10 Feb 2023 14:47:38 +0000 [thread overview] Message-ID: <bug-29742-4717-oUnVrCSmWr@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29742-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29742 --- Comment #9 from Libin Dang <libin.dang at gmail dot com> --- Backtrace of gdbserver: (gdb) bt #0 0x76c7e216 in ?? () from /lib/libc.so.6 #1 0x76c8c9d4 in raise () from /lib/libc.so.6 #2 0x76c7dca0 in abort () from /lib/libc.so.6 #3 0x0041f1e0 in abort_or_exit () at ../../gdb-14.0.50.20230201/gdbserver/utils.cc:39 #4 internal_verror (file=<optimized out>, line=line@entry=2448, fmt=0x0, fmt@entry=0x7ec8e2bc "\260KF", args=..., args@entry=...) at ../../gdb-14.0.50.20230201/gdbserver/utils.cc:108 #5 0x0044fd32 in internal_error_loc (file=<optimized out>, line=line@entry=2448, fmt=0x45c8b0 "%s. Switching to stderr.\n") at ../../gdb-14.0.50.20230201/gdbsupport/errors.cc:58 #6 0x0043cfbc in linux_process_target::maybe_hw_step (this=<optimized out>, thread=<optimized out>) at ../../gdb-14.0.50.20230201/gdbserver/linux-low.cc:2448 #7 linux_process_target::maybe_hw_step (this=<optimized out>, thread=<optimized out>) at ../../gdb-14.0.50.20230201/gdbserver/linux-low.cc:2440 #8 0x0043d99e in linux_process_target::resume_stopped_resumed_lwps (this=this@entry=0x4821ec <the_arm_target>, thread=0x9c17d0) at ../../gdb-14.0.50.20230201/gdbserver/linux-low.cc:2466 #9 0x0043e9ac in <lambda(thread_info*)>::operator() (__closure=<synthetic pointer>, thread=<optimized out>) at ../../gdb-14.0.50.20230201/gdbserver/linux-low.cc:2606 #10 for_each_thread<linux_process_target::wait_for_event_filtered(ptid_t, ptid_t, int*, int)::<lambda(thread_info*)> > (func=...) at ../../gdb-14.0.50.20230201/gdbserver/gdbthread.h:159 #11 linux_process_target::wait_for_event_filtered (this=this@entry=0x4821ec <the_arm_target>, wait_ptid=..., filter_ptid=..., wstatp=0x7ec8e544, options=1073741824) at ../../gdb-14.0.50.20230201/gdbserver/linux-low.cc:2604 #12 0x00440e2a in linux_process_target::wait_for_event (options=1078469316, wstatp=0x7ec8e544, ptid=..., this=0x4821ec <the_arm_target>) at ../../gdb-14.0.50.20230201/gdbserver/linux-low.cc:2676 #13 linux_process_target::wait_1 (this=this@entry=0x4821ec <the_arm_target>, ptid=..., ourstatus=ourstatus@entry=0x484818 <g_client_state+1288>, target_options=..., target_options@entry=...) at ../../gdb-14.0.50.20230201/gdbserver/linux-low.cc:2970 #14 0x0044256c in linux_process_target::wait (this=0x4821ec <the_arm_target>, ptid=..., ourstatus=0x484818 <g_client_state+1288>, target_options=...) at ../../gdb-14.0.50.20230201/gdbserver/linux-low.cc:3624 #15 0x00430a1c in target_wait (options=..., status=0x484818 <g_client_state+1288>, ptid=...) at ../../gdb-14.0.50.20230201/gdbserver/target.cc:199 #16 mywait (ptid=..., ourstatus=ourstatus@entry=0x484818 <g_client_state+1288>, options=..., connected_wait=connected_wait@entry=1) at ../../gdb-14.0.50.20230201/gdbserver/target.cc:144 #17 0x0042a6c0 in resume (actions=<optimized out>, num_actions=<optimized out>) at ../../gdb-14.0.50.20230201/gdbserver/server.cc:2917 #18 resume (actions=0x9d4b18, num_actions=<optimized out>) at ../../gdb-14.0.50.20230201/gdbserver/server.cc:2889 #19 0x0042b168 in handle_v_cont (own_buf=0x9d4b18 "<\001") at ../../gdb-14.0.50.20230201/gdbserver/server.cc:2876 #20 handle_v_requests (own_buf=own_buf@entry=0x9b50a8 "vCont;r45b52a,45b52c:p13c.17d;c:p13c.-1", packet_len=packet_len@entry=39, new_packet_len=new_packet_len@entry=0x7ec8e8ac) at ../../gdb-14.0.50.20230201/gdbserver/server.cc:3136 #21 0x0042de1e in process_serial_event () at ../../gdb-14.0.50.20230201/gdbserver/server.cc:4482 #22 handle_serial_event (err=<optimized out>, client_data=<optimized out>) at ../../gdb-14.0.50.20230201/gdbserver/server.cc:4514 #23 0x0045026c in gdb_wait_for_event (block=block@entry=1) at ../../gdb-14.0.50.20230201/gdbsupport/event-loop.cc:694 #24 0x0045099c in gdb_wait_for_event (block=1) at ../../gdb-14.0.50.20230201/gdbsupport/event-loop.cc:593 #25 gdb_do_one_event (mstimeout=mstimeout@entry=-1) at ../../gdb-14.0.50.20230201/gdbsupport/event-loop.cc:264 #26 0x0041f9cc in start_event_loop () at ../../gdb-14.0.50.20230201/gdbserver/server.cc:3512 #27 captured_main (argv=<optimized out>, argc=4) at ../../gdb-14.0.50.20230201/gdbserver/server.cc:3992 #28 main (argc=4, argv=<optimized out>) at ../../gdb-14.0.50.20230201/gdbserver/server.cc:4078 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-10 14:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-02 15:50 [Bug gdb/29742] New: " libin.dang at gmail dot com 2022-11-03 8:32 ` [Bug gdb/29742] " luis.machado at arm dot com 2022-11-03 15:33 ` libin.dang at gmail dot com 2022-11-03 16:45 ` luis.machado at arm dot com 2022-11-10 10:35 ` libin.dang at gmail dot com 2022-11-10 10:37 ` libin.dang at gmail dot com 2022-11-10 10:45 ` libin.dang at gmail dot com 2022-11-21 16:25 ` libin.dang at gmail dot com 2022-11-29 13:19 ` jeroen.hiddink at vialis dot nl 2023-02-10 14:45 ` libin.dang at gmail dot com 2023-02-10 14:47 ` libin.dang at gmail dot com [this message] 2023-02-10 14:50 ` libin.dang at gmail dot com
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-29742-4717-oUnVrCSmWr@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).