public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert K Gjertsen <gjertsen@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] question on stabs option being disabled with ia64
Date: Mon, 17 Mar 2003 21:03:37 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709806138@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806141@msgid-missing>

This is a multipart message in MIME format.
--=_alternative 00528CE486256CEC_Content-Type: text/plain; charset="us-ascii"

I was wondering if someone could provide some insight on why
the stabs support for ia64 was disabled in gcc 3.1.
My understanding is that DWARF2 is the default debugging format on 
ia64-linux,
yet it was once possible to configure ia64 gcc to use stabs instead of
DWARF2, and it's still possible to use stabs on i686-linux and 
powerpc64-linux.

This is motived by my interest in LKCD, which depends on stabs.
I'm trying to determine whether it will take more work to fix ia64 gcc
or make LKCD use DWARF2 with ia64 (for lcrash) and would appreciate any
pointers.
KDB is fine for in-house debugging, but it isn't the preferred method on
customer systems.

Thanks,

--Rob
--=_alternative 00528CE486256CEC_Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="Courier New">I was wondering if someone could provide some insight on why</font>
<br><font size=2 face="Courier New">the stabs support for ia64 was disabled in gcc 3.1.</font>
<br><font size=2 face="Courier New">My understanding is that DWARF2 is the default debugging format on ia64-linux,</font>
<br><font size=2 face="Courier New">yet it was once possible to configure ia64 gcc to use stabs instead of</font>
<br><font size=2 face="Courier New">DWARF2, and it's still possible to use stabs on i686-linux and powerpc64-linux.</font>
<br>
<br><font size=2 face="Courier New">This is motived by my interest in LKCD, which depends on stabs.</font>
<br><font size=2 face="Courier New">I'm trying to determine whether it will take more work to fix ia64 gcc</font>
<br><font size=2 face="Courier New">or make LKCD use DWARF2 with ia64 (for lcrash) and would appreciate any</font>
<br><font size=2 face="Courier New">pointers.</font>
<br><font size=2 face="Courier New">KDB is fine for in-house debugging, but it isn't the preferred method on</font>
<br><font size=2 face="Courier New">customer systems.</font>
<br>
<br><font size=2 face="Courier New">Thanks,</font>
<br>
<br><font size=2 face="Courier New">--Rob</font>
--=_alternative 00528CE486256CEC_=--


      parent reply	other threads:[~2003-03-17 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17 15:29 [Linux-ia64] question on stabs option being disabled with ia64 Andreas Schwab
2003-03-17 17:34 ` jim
2003-03-17 21:03 ` Robert K Gjertsen [this message]

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=marc-linux-ia64-105590709806138@msgid-missing \
    --to=gjertsen@us.ibm.com \
    --cc=linux-ia64@vger.kernel.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