public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: snowball3@bigfoot.com
Cc: djgpp-workers@delorie.com, binutils@sourceware.cygnus.com
Subject: Re: Another script for building binutils
Date: Wed, 28 Jul 1999 22:13:00 -0000	[thread overview]
Message-ID: <19990729020624.1145.qmail@daffy.airs.com> (raw)
In-Reply-To: <199907290027.AAA82496@out5.ibm.net>

   From: "Mark E." <snowball3@bigfoot.com>
   Date: Wed, 28 Jul 1999 20:27:45 -0400

   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.

Run objdump -xs on both files, and see what changed.

Ian

  reply	other threads:[~1999-07-28 22:13 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.
1999-07-28 22:13   ` Ian Lance Taylor [this message]
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=19990729020624.1145.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=djgpp-workers@delorie.com \
    --cc=snowball3@bigfoot.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).