public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/28580] put breakpoint using line *and* column
Date: Wed, 10 Nov 2021 14:32:15 +0000	[thread overview]
Message-ID: <bug-28580-4717-3JeMvzmyAh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28580-4717@http.sourceware.org/bugzilla/>

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

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simark at simark dot ca

--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
GCC has enabled column numbers in debug info a few years ago, and I think clang
had them a while also.  GDB was never updated to leverage that, it's just
waiting for somebody to do the work.  In addition to allow putting breakpoints
on line:column locations, it was proposed to have new step-like commands to
step "statements", which would step until reaching a new column / location,
even if on the same line.

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

  reply	other threads:[~2021-11-10 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 14:15 [Bug breakpoints/28580] New: " b2.temp at gmx dot com
2021-11-10 14:32 ` simark at simark dot ca [this message]
2021-11-10 17:52 ` [Bug breakpoints/28580] " garminhelp24x7 at gmail dot com
2024-01-09 17:03 ` 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-28580-4717-3JeMvzmyAh@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).