From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23819 invoked by alias); 2 Apr 2004 19:42:25 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 23770 invoked from network); 2 Apr 2004 19:42:24 -0000 Received: from unknown (HELO aragorn.inter.net.il) (192.114.186.23) by sources.redhat.com with SMTP; 2 Apr 2004 19:42:24 -0000 Received: from zaretski ([80.230.154.15]) by aragorn.inter.net.il (MOS 3.4.5-GR) with ESMTP id CQW21826; Fri, 2 Apr 2004 21:42:09 +0200 (IST) Date: Fri, 02 Apr 2004 19:42:00 -0000 From: "Eli Zaretskii" To: Brian Ford Message-Id: <2719-Fri02Apr2004213907+0300-eliz@gnu.org> CC: jimb@redhat.com, gdb-patches@sources.redhat.com In-reply-to: (message from Brian Ford on Fri, 2 Apr 2004 11:31:33 -0600 (CST)) Subject: Re: [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp) Reply-to: Eli Zaretskii References: <8011-Fri02Apr2004094123+0300-eliz@gnu.org> X-SW-Source: 2004-04/txt/msg00066.txt.bz2 > Date: Fri, 2 Apr 2004 11:31:33 -0600 (CST) > From: Brian Ford > > > > > > This isn't really relevant > > > > Why not? > > Well first, it's not really Windows, it's DOS. Secondly, it's pure > COFF with a custom loader, as I understand, not PE/COFF. Yes, true on both counts. I guess I misunderstood the meaning of ``relevant'' in your original message. > I just don't see any reason to try and be "compatible" with it. I'm not > even sure what that means? I certainly don't want to break it, > though. Well, the only way to break DJGPP is if you modify code used by it as well. So any pieces of coffread.c or dwarf2read.c, or anything in i386-related files that is related to that, are possible areas of interest. If you only change Windows-specific files, you cannot possibly break DJGPP (or any other non-Windows target). However, what I'm really interested in is the possibility that a similar problem exists in the DJGPP port. > > 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. > > > You mean source code, right? You would obviously need a DJGPP toolchain > for testing. I don't have one right now. Well, I do have it, obviously: otherwise, how could I possibly be maintaining the DJGPP port of GDB? ;-) > A sample program would be trivial, so you might as well make one yourself. > Just throw in some stack variables, preferably some in main, and some in > a function called from main. Oh, and make a few of them floating point > so you can test that too. I understand this, but given my total lack of free time, I'd appreciate a specific worked-out example with commands you type and what GDB prints in response. I don't mean for you to install the DJGPP development environment and try that, just do that with the Windows tools where you encountered the problem. All I want to see is whether similar problems with EBP and ESP exist in the DJGPP port. Of course, if you are not interested to see whether other i386 targets have this problem, you are free to disregard my request. Thanks in advance.