Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: y2bismil@engmail.uwaterloo.ca
To: gdb@sources.redhat.com
Subject: Re: open watcom
Date: Thu, 18 Sep 2003 20:34:00 -0000	[thread overview]
Message-ID: <1063917298.3f6a16f208b35@www.nexusmail.uwaterloo.ca> (raw)
In-Reply-To: <200309182025.h8IKPu7G031931@duracef.shout.net>

Thanks Michael,

open watcom does support dwarf1, and so I tried that, but still nothing.  GDB 
just keeps saying it can't find any debug information.  Shuold gdb 
automatically detect the debug type, or is there an option?

Thanks

Quoting Michael Elizabeth Chastain <mec@shout.net>:
> > Does anyone know the location of a list of supported debug format by gdb?
> 
> dwarf 1, dwarf 1+
> dwarf 2
> stabs, stabs+
> coff, xcoff, xcoff+
> mdebug
> 
> Also, I'm not sure whether "hp" is an object code format or a debug
> format.
> 
> Michael C
> 


Quoting Michael Elizabeth Chastain <mec@shout.net>:

> > Does anyone know the location of a list of supported debug format by gdb?
> 
> dwarf 1, dwarf 1+
> dwarf 2
> stabs, stabs+
> coff, xcoff, xcoff+
> mdebug
> 
> Also, I'm not sure whether "hp" is an object code format or a debug
> format.
> 
> Michael C
> 




----------------------------------------
This mail sent through www.mywaterloo.ca


  parent reply	other threads:[~2003-09-18 20:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 20:25 Michael Elizabeth Chastain
2003-09-18 20:29 ` Joel Brobecker
2003-09-18 20:34 ` y2bismil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-19 14:50 vast numbers of unimplemented MI commands Alain Magloire
2003-09-19 14:53 ` open watcom y2bismil
2003-09-18 21:54 Michael Elizabeth Chastain
2003-09-18 21:11 Michael Elizabeth Chastain
2003-09-18 21:20 ` y2bismil
2003-09-18 22:44   ` Jim Blandy
2003-09-18 20:21 y2bismil

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=1063917298.3f6a16f208b35@www.nexusmail.uwaterloo.ca \
    --to=y2bismil@engmail.uwaterloo.ca \
    --cc=gdb@sources.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