public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Bartosz Nitka <niteria@gmail.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3 0/1] Don't rewind PC for GHC generated frames
Date: Mon, 12 Feb 2018 13:50:00 -0000	[thread overview]
Message-ID: <CAH=s-PPFSafb123n2shgwQciRXO8rgUqoOszXyvMNYfP9R4aVA@mail.gmail.com> (raw)
In-Reply-To: <20180204000647.19188-1-niteria@gmail.com>

On Sun, Feb 4, 2018 at 12:06 AM, Bartosz Nitka <niteria@gmail.com> wrote:
> As a side note, Haskell code can be pretty dense and a lot
> of functionality can fit on one line. GHC already puts column
> numbers in the debugging information, but from what I can tell
> GDB doesn't expose that in any way.
> Would that be a worthwhile addition to GDB?

If what you meant is DW_LNS_set_column, then, other compilers
also generates it, and GDB doesn't use it.  Maybe, GDB can use
it in TUI mode, to blink on the right line and column, or GDB tells
MI front ends the column number so they can highlight accordingly.
What do you want to add to GDB?

-- 
Yao (齐尧)

  parent reply	other threads:[~2018-02-12 13:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04  0:07 Bartosz Nitka
2018-02-04  0:07 ` [PATCH v3 1/1] " Bartosz Nitka
2018-02-12 12:35   ` Bartosz Nitka
2018-02-12 15:44   ` Simon Marchi
2018-02-19 13:10     ` Bartosz Nitka
2018-02-19 17:02       ` Simon Marchi
2018-02-12 13:50 ` Yao Qi [this message]
2018-02-12 14:14   ` [PATCH v3 0/1] " Bartosz Nitka
2018-02-12 14:42     ` Yao Qi
2018-02-19 13:27       ` Bartosz Nitka

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='CAH=s-PPFSafb123n2shgwQciRXO8rgUqoOszXyvMNYfP9R4aVA@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=niteria@gmail.com \
    /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).