public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: zap@cobra.ru
To: gcc-gnats@gcc.gnu.org
Cc: platon@innotek.de (Platon Fomichev)
Subject: driver/10369: Not removing object file on Ctrl+C and not using a space between "-o" and object name
Date: Thu, 10 Apr 2003 14:06:00 -0000	[thread overview]
Message-ID: <20030410140441.9223.qmail@sources.redhat.com> (raw)


>Number:         10369
>Category:       driver
>Synopsis:       Not removing object file on Ctrl+C and not using a space between "-o" and object name
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 10 14:06:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Andrew Zabolotny
>Release:        gcc 3.2.2
>Organization:
>Environment:
OS/2 EMX
>Description:
The driver has a bug that prevents it from deleting incomplete object files on pressing Ctrl+C. This happens ONLY when not using a space betwen "-o" and the file name (e.g.
"-ofile.o"). This is very easy to reproduce by generating a large .c file (I did it with a simple shell script) and while it compiles, press Ctrl+C. The file.o file will remain; this is bad since it confuses make.

I've tracked the problem: it is in gcc.c when executing the 'W' spec, it calls add_temporary_file_name or such (don't remember the exact function name, don't have the sources handy). The name that is passed to the function includes the -o switch (e.g. add_temporary_file_name ("-ofile.o")) and on failure the driver tries to delete the file with this name, and naturally fails.
>How-To-Repeat:
gcc -c -ofile.o file.c
>Fix:
Not sure, this requires deep knowledge of how specs are parsed and executed. A quick-and-dirty patch is possible, but I presume whoever knows the internals will do it a lot better.
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-04-10 14:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030410140441.9223.qmail@sources.redhat.com \
    --to=zap@cobra.ru \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=platon@innotek.de \
    /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).