public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Doug Evans'" <dje@google.com>
Cc: "'Pedro Alves'" <palves@redhat.com>,
	"'gdb-patches'" <gdb-patches@sourceware.org>
Subject: RE: [RFA PATCH 2/3] Add debug-stabs debug-dwarf and class option for pascal compiler
Date: Sat, 10 Jan 2015 00:55:00 -0000	[thread overview]
Message-ID: <004a01d02c70$27cf9820$776ec860$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <CADPb22TZH+Ab6xLi_pKspY1xeh76Ms7G5r2r_KcMEHn2pWd2tw@mail.gmail.com>

> Hi.
> This patch makes me uncomfortable.
> It's to a pascal specific file, so at least the discomfort is contained
> :-),
> but I wouldn't want this spreading.
> 
> How to select debug information should be
> orthogonal to compilation language,
> and there are a myriad of ways to select what kind of dwarf debug info
> to get (with/without type units, with/without .gdb_index, with/without
> dwz, and so on).  I have board files to help me drive the various
> combinations I'm interested in.  This won't work if gdb.pascal/*
> starts hardcoding debug info into the test.
> 
> Maybe there's a good reason to do it this way for pascal,
> but I need more data.

 Hi Doug, the reasons of this patch are:

1) the particular problem that the series fixes is strictly limited
to stabs debugging information.

  Thus to really test that this bug has been fixed, I need to compile
the test code using stabs debugging format (which I now realize
I did not do in the third part of the patch series).

2) the pascal language support tries to support both
GNU pascal compiler (aka GPC) and Free Pascal Compiler (aka FPC).

  These two compilers have very different options,
so the submitted patch purpose is to unify the selection of stabs versus dwarf
debug format independently from the used pascal compiler.

 For other pascal tests, only debug is used, which results in the default
format according to the target architecture and operating system.

I hope that the explanations above are sufficient to ease your discomfort.


Pierre Muller 

  reply	other threads:[~2015-01-10  0:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54ae4586.01e3440a.7b06.fffff844SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-08 10:48 ` [RFA] Fix pascal behavior for class fields Pedro Alves
2015-01-08 13:01   ` Pierre Muller
     [not found]   ` <54ae7f9f.c323460a.36ed.ffffff30SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-08 13:41     ` Pedro Alves
2015-01-08 14:15       ` gdb-patches RFA: " Pierre Muller
     [not found]       ` <54ae911b.85e3440a.1d96.5ffdSMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-09 10:52         ` Pedro Alves
2015-01-09 10:55           ` Pedro Alves
2015-01-09 16:16           ` [RFA PATCH 1/3] Remember the case pattern that allowed finding a field of this Pierre Muller
2015-01-23  7:30             ` [RFA PATCH 1/3 V3] " Pierre Muller
2015-02-04 23:37               ` [RFA PATCH 1/3 V4] " Pierre Muller
2015-01-09 16:16           ` [RFA 0/3] Fix pascal behavior for class fields with testcase Pierre Muller
2015-01-09 16:18             ` [RFA PATCH 2/3] Add debug-stabs debug-dwarf and class option for pascal compiler Pierre Muller
2015-02-04 23:37             ` [RFA 0/3 V4] Fix pascal behavior for class fields with testcase Pierre Muller
2015-02-15  6:59               ` PING " Pierre Muller
2015-04-07 20:06                 ` PING^2 " Pierre Muller
     [not found]               ` <54e043b2.626ec20a.0c59.ffffaeacSMTPIN_ADDED_BROKEN@mx.google.com>
2015-04-20  6:00                 ` PING " Doug Evans
2015-04-21 20:33                   ` Pierre Muller
2015-01-09 16:18           ` [RFA PATCH 3/3] Testcase for pascal/17815 Pierre Muller
     [not found]           ` <54afff61.6790420a.0fa7.4f63SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-10  0:45             ` [RFA PATCH 2/3] Add debug-stabs debug-dwarf and class option for pascal compiler Doug Evans
2015-01-10  0:55               ` Pierre Muller [this message]
     [not found]               ` <54b07891.01b3c20a.2a7b.ffff9f96SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-10 21:23                 ` Doug Evans
2015-01-14 15:04                   ` [RFA PATCH 2/3 V2] Add "class" " Pierre Muller
     [not found]                   ` <54b6858f.a287440a.5b61.ffff9ef0SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-22 12:49                     ` Pedro Alves
2015-01-23  5:21                       ` [RFA PATCH 2/3 V3] " Pierre Muller
2015-01-23 11:55                         ` Pedro Alves
2015-02-04 23:37                           ` [RFA PATCH 2/3 V4] " Pierre Muller
     [not found]           ` <54afff6b.ee8d440a.16ee.ffffb424SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-22 12:46             ` [RFA PATCH 3/3] Testcase for pascal/17815 Pedro Alves
2015-01-23  7:16               ` [RFA PATCH 3/3 V3] " Pierre Muller
2015-01-23 12:29                 ` Pedro Alves
2015-02-04 23:37                   ` [RFA PATCH 3/3 V4] " Pierre Muller

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='004a01d02c70$27cf9820$776ec860$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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).