Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Brian Ford <ford@vss.fsi.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jimb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp)
Date: Mon, 05 Apr 2004 22:46:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.58.0404051658560.21204@thing1-200> (raw)
In-Reply-To: <6654-Sat03Apr2004110513+0300-eliz@gnu.org>

On Sat, 3 Apr 2004, Eli Zaretskii wrote:

> On Fri, 2 Apr 2004, Brian Ford wrote:
>
> > Ok, I'm trying to find a simple step-by-step.
>
> Thank you.

Jim beat me to it.

> > As a quick test, does a simple "bt" for a DWARF 2 compiled program stop at
> > main, or run off infinately?
>
> It stops at main.  Here's a session transcript, using the test
> program from the message you referred to:

I realized this morning that this problem only happens in DWARF 2 if your
ebp and esp are reversed.  DJGPP's are ok in DWARF 2, just not in stabs.
 See Jim's example and my response for how to test that.  Thanks for
testing anyway.

> > Can you try Jim's example program here compiled for DWARF 2?

and STABS?

> > http://sources.redhat.com/ml/gdb-patches/2004-04/msg00025.html
> >
> > Try an info address a in foo and see what you get.
>
> I get the following, no matter whether I compile with "-gstabs+" or
> "-gdwarf-2":
>
> (gdb) info address a
> Symbol "a" is a variable in register st4.

I'm sorry, but are you sure you get the same register number in both
cases?  I don't see how that can be given my current understanding of the
issues.

> > Also, can you confirm the dumped DWARF info has a DW_AT_frame_base of
> > DW_OP_reg4, not 5?

Please check it for foo and main if you do this.

> I cannot use readelf here, since DJGPP binaries are COFF files, not
> ELF files.  Is there a way to do this using objdump?

No, see Jim's reply.

I do have a hacked version of dwarfdump that works on COFF files.  Let me
know if you are interested and would trust me to send you the executable
directly.

> > How often does DJGPP use sdb, stabs, dwarf 2?
>
> I don't have statistics (but see below).  I myself use all of them
> roughly the same.

Yeah, I just meant relatively.

> > I just realized that DWARF 2 is not the default.
>
> Well, it is in DJGPP: GCC 3.2 and later use DWARF-2 by default.  So I
> guess, for the random DJGPP user, DWARF-2 is much more frequent these
> days that either -gstabs+ or -gcoff.

I'm confused here.  I just did another pass through the gcc sources
(3.4 branch in this case) and looked at all the djgpp config files:
ford@fordpc ~/downloads/gcc/gcc/config

$ fgrep DEBUGGING i386/xm-djgpp.h i386/i386.h dbxcoff.h i386/unix.h
i386/bsd.h i386/gas.h i386/djgpp.h
dbxcoff.h:#define DBX_DEBUGGING_INFO 1
dbxcoff.h:#ifndef PREFERRED_DEBUGGING_TYPE
dbxcoff.h:#define PREFERRED_DEBUGGING_TYPE SDB_DEBUG
i386/gas.h:#define SDB_DEBUGGING_INFO 1
i386/djgpp.h:#define DWARF2_DEBUGGING_INFO 1

That makes it appear that the default debugging type is SDB_DEBUG (coff).
I've got to be missing something obvious here?

Thanks again for your time.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444


  parent reply	other threads:[~2004-04-05 22:46 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  0:11 Brian Ford
2004-04-01 17:22 ` Jim Blandy
2004-04-01 18:00   ` Brian Ford
2004-04-01 21:29     ` Jim Blandy
2004-04-01 22:54       ` Brian Ford
2004-04-02  7:45         ` Eli Zaretskii
     [not found]           ` <Pine dot GSO dot 4 dot 58 dot 0404021000390 dot 21204 at thing1-200>
     [not found]             ` <2719-Fri02Apr2004213907+0300-eliz at gnu dot org>
     [not found]               ` <Pine dot GSO dot 4 dot 58 dot 0404021648050 dot 21204 at thing1-200>
2004-04-02 17:31           ` Brian Ford
2004-04-02 19:42             ` Eli Zaretskii
2004-04-02 23:15               ` Brian Ford
2004-04-03  9:08                 ` Eli Zaretskii
2004-04-05 18:18                   ` Jim Blandy
2004-04-05 21:57                     ` Brian Ford
2004-04-18 16:33                       ` Eli Zaretskii
2004-04-05 18:21                   ` Jim Blandy
2004-04-05 22:46                   ` Brian Ford [this message]
2004-04-18 17:00                     ` Eli Zaretskii
2004-04-05 22:46                 ` Jim Blandy
2004-04-05 23:19                   ` Brian Ford
2004-04-05 23:38                     ` Jim Blandy
2004-04-06 14:53                       ` Brian Ford
2004-04-15  9:38                         ` Eli Zaretskii
2004-04-06 23:24                     ` Mark Kettenis
2004-04-07 16:25                       ` Brian Ford
2004-04-07 18:02                         ` Jim Blandy
2004-04-07 20:06                       ` [PATCH] Rename i386_xxx_reg_to_regnum Brian Ford
2004-04-07 20:48                         ` Jim Blandy
2004-04-07 21:06                           ` Brian Ford
2004-04-07 21:41                             ` Jim Blandy
2004-04-09 12:37                               ` Mark Kettenis
2004-04-09 17:49                                 ` Brian Ford
2004-04-06 23:23                   ` [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp) Mark Kettenis
2004-04-07 16:46                     ` Jim Blandy
2004-04-18 16:48                   ` Eli Zaretskii
2004-04-19  2:06                     ` ix86 PE/COFF DWARF register numbering (was Re: [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp)) Brian Ford
2004-04-19  5:59                       ` Eli Zaretskii
2004-04-19 16:34                         ` ix86 PE/COFF DWARF register numbering Brian Ford
2004-04-19 12:42                     ` [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp) Jim Blandy
2004-04-19  7:02                       ` Eli Zaretskii
2004-04-02 19:33           ` Eli Zaretskii
2004-04-02 22:47             ` Brian Ford

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=Pine.GSO.4.58.0404051658560.21204@thing1-200 \
    --to=ford@vss.fsi.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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