From: "Eli Zaretskii" <eliz@gnu.org>
To: Brian Ford <ford@vss.fsi.com>
Cc: jimb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp)
Date: Fri, 02 Apr 2004 07:45:00 -0000 [thread overview]
Message-ID: <8011-Fri02Apr2004094123+0300-eliz@gnu.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0404011553100.21204@thing1-200> (message from Brian Ford on Thu, 1 Apr 2004 16:54:46 -0600 (CST))
> Date: Thu, 1 Apr 2004 16:54:46 -0600 (CST)
> From: Brian Ford <ford@vss.fsi.com>
> >
> > Sorry --- is there an existing toolchain using Dwarf 2 on Windows? If
> > not, then what existing tools, already in use by others, are you being
> > forward and backward compatible with?
> >
> This isn't really relevant
Why not?
> but DJGPP does.
That's true: DJGPP does support DWARF2 debug info in COFF object file
format.
> It appears to me that they use the dbx_register_map for DWARF2. So,
> I don't understand why they don't have the problem my patch was
> trying to address.
I marked this thread for checking, but never had time to do it. If
you can send me a sample program and a description of what I should do
to see whether DJGPP has the same problem, I will gladly try that and
report the results. Please also tell what versions of GCC and GDB
should I try.
> The forward part of my compatability argument is that all known working
> (I still don't understand how DJGPP is working without my patch) i386 targets
> with DWARF2 support use the svr4_register_numbering scheme. So, I was
> trying to go with that precident instead of the one you observed.
Some time ago I did find a problem in register numbering, and IIRC it
was fixed, although I don't recall the details and don't see anything
in the logs. Perhaps the fix was in GCC rather than GDB. And I don't
remember whether I looked at EBP and ESP back then.
next prev parent reply other threads:[~2004-04-02 7:45 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 [this message]
[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
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=8011-Fri02Apr2004094123+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=ford@vss.fsi.com \
--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