public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Subject: Re: Defaulting to stabs debug output from AS Cygwin64
Date: Tue, 15 May 2018 17:41:00 -0000	[thread overview]
Message-ID: <CAOC2fq-fhFXBPBVFWNQpqUeKZf-2KFowUeAzv9xkBSDQud=1zg@mail.gmail.com> (raw)
In-Reply-To: <551ec1bb-60e2-2372-8e1a-f4cb839ae454@gmail.com>

On Tue, May 15, 2018 at 5:58 AM, cyg Simple <cygsimple@gmail.com> wrote:
>
> Years of work tells me to not trust the default of any option.  You
> should be specific.

I have a few years under my belt (come to think of it they are
threatening to engulf my belt). For work, I'd do what's necessary to
integrate the little thing into the big thing. For this I don't want
to work too hard on side issues unless I decide they are interesting
side issues.

>
> The dwarf format isn't supported by native tools.  I think COFF should
> be the default but that is just me and I don't maintain the distribution
> of GCC.

The GCC driver uses -gdwarf2 if you do 'gcc -g' on a .s file. Using
-gdwarf2 with assembly code manually or through gcc is successful in
producing a Cygwin64 executable that Cygwin64 GDB can work with. This
combination of circumstances led me to wonder how stabs was chosen for
Cygwin64.

>
> I question your use of Cygwin instead of MinGW for your compiler but
> that is just a musing.
>

When I cobble together an I/O system for the language's runtime, I
will probably switch the project to Linux-only. I/O is one of the
interesting side issues I wish to tackle.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-05-15 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 12:49 Michael Enright
2018-05-15 13:18 ` cyg Simple
2018-05-15 17:41   ` Michael Enright [this message]
2018-05-15 21:18     ` Hans-Bernhard Bröker

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='CAOC2fq-fhFXBPBVFWNQpqUeKZf-2KFowUeAzv9xkBSDQud=1zg@mail.gmail.com' \
    --to=mike@kmcardiff.com \
    --cc=cygwin@cygwin.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).