public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "aakash0641 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/28906] New: GDB debugger hangs after step call
Date: Fri, 18 Feb 2022 14:07:22 +0000	[thread overview]
Message-ID: <bug-28906-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28906

            Bug ID: 28906
           Summary: GDB debugger hangs after step call
           Product: gdb
           Version: 9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: aakash0641 at gmail dot com
  Target Milestone: ---

The bug and details to produce are in the following link:
https://github.com/microsoft/vscode-cpptools/issues/8776#issuecomment-1043482104

GDB debugger hangs on the step call (using F5 or F10 or F11). 

Repro steps:

     Check out https://github.com/whoenig/libMultiRobotPlanning
     Install dependencies (see InstallPackagesUbuntu as an example.
     Add -g to CMAKE_CXX_FLAGS in CMakeLists.txt
     Build as described in README
     Debug with just GDB
         gdb ecbs_ta
         break next_best_assignment.hpp:53
         r -i ../benchmark/8x8_obst12/map_8by8_obst12_agents1_ex0.yaml -o
../ofile_1.yaml
         continue
         step


It will hang after the step call.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-02-18 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 14:07 aakash0641 at gmail dot com [this message]
2022-02-18 14:07 ` [Bug c++/28906] " aakash0641 at gmail dot com
2022-02-18 14:10 ` aakash0641 at gmail dot com
2022-02-18 14:20 ` simark at simark dot ca
2022-02-18 15:18 ` aakash0641 at gmail dot com
2022-02-18 15:23 ` simark at simark dot ca
2022-02-18 16:16 ` aakash0641 at gmail dot com
2022-02-18 16:26 ` simark at simark dot ca

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-28906-4717@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: 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).