public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "peffyd at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/28411] New: breakpoint sets in wrong line and crashes when attempting to RUN or START
Date: Sat, 02 Oct 2021 03:45:17 +0000 [thread overview]
Message-ID: <bug-28411-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28411
Bug ID: 28411
Summary: breakpoint sets in wrong line and crashes when
attempting to RUN or START
Product: gdb
Version: 10.1
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: peffyd at yahoo dot com
Target Milestone: ---
Surface Book 2 Using windows 10 pro 20H2
installed with mysys2
GCC version 10.3
GDB version 10.2
I was successfully able to debug the same file in Mac but, when I attempt on
windows it crashes.
MAC compiled using with -ggdb flag. NOTE Mac is running GDB version 11.0
Windows compiled using GCC with -g flag. Also tried -g -O0 but it still crashed
In windows GDB is able to start and I am able to view the file, layout src.
When attempting to add breakpoint such as break main or break <linenumber> sets
breakpoint to wrong line. It sets it a few lines below and does not allow me to
set a breakpoint above the line number that is selected. When attempting to run
or start GDB it crashes the terminal. I have attempted to run from command
prompt and powershell. Both crash!
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-10-02 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 3:45 peffyd at yahoo dot com [this message]
2021-10-02 3:52 ` [Bug breakpoints/28411] " peffyd at yahoo dot com
2024-01-09 17:47 ` ssbssa at sourceware dot 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-28411-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).