From: "Mark E." <snowball3@bigfoot.com>
To: djgpp-workers@delorie.com, binutils@sourceware.cygnus.com
Subject: Re: Another script for building binutils
Date: Wed, 28 Jul 1999 17:27:00 -0000 [thread overview]
Message-ID: <199907290027.AAA82496@out5.ibm.net> (raw)
In-Reply-To: <B0000096305@stargate.astr.lu.lv>
> Last test were done with binutils snapshots (990727 appears to be
> bad: broken debug info, so I'll perhaps return to 990710 which I
> used for some time).
Hi Andris,
I'm also sending this to binutils so perhaps we can get some help. I
did some testing and found that compiling with -g (for COFF
debugging) doesn't work properly while using -gstabs+ will work with
my sample C program.
How I tested:
I compiled a small C program to an .s file using 'gcc -gstabs+ -S
main.c'. I then used the as.exe from Dec '98 to generate a .o file and an
as.exe from July 26th to do the same but with a different filename. I
was able to step through the generated executables derived from both
.o files with rhgdb.exe.
I then generated another .s file using 'gcc -g -S main.c' and repeated
the generation of the two .o files. I could debug the main.exe derived
from the Dec. '98 as.exe generated .o file. However, I could only step
one line into the main.exe derived from the Jul. 26th generated .o file.
Andris, is this something like what you found?
If this is something that only happened very recently, the cause should
be easily traceable.
BTW, I made sure to disable long section support and my alignment
patch #2 before testing.
Mark
---
Mark Elbrecht, snowball3@bigfoot.com
http://snowball.frogspace.net/
next parent reply other threads:[~1999-07-28 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B0000096305@stargate.astr.lu.lv>
1999-07-28 17:27 ` Mark E. [this message]
1999-07-28 22:13 ` Ian Lance Taylor
1999-07-28 20:52 Mark E.
1999-07-29 11:29 ` Ian Lance Taylor
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=199907290027.AAA82496@out5.ibm.net \
--to=snowball3@bigfoot.com \
--cc=binutils@sourceware.cygnus.com \
--cc=djgpp-workers@delorie.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).