gcc and creating a debug file

xviddivxoggmp3 · 03-16-2004, 02:38 AM

is there any switch you place after the gcc to make it create a file on the a: drive that has all the compiler errors?

syntax similar to

gcc [switch] [file path and name]

jinksys · 03-16-2004, 03:03 AM

Assuming your a: drive is mounted at /mnt/floppy

Code:

gcc filetocompile.c &> /mnt/floppy/errors

Thats the simplist route I can see, since "errors" will only have content when something
goes wrong, unless of course you use a switch like -v , in that case all messages will be
sent to "errors".

hypexr · 03-16-2004, 03:04 AM

I think that gcc filename 2>/mnt/floppy/error_log might be what you are looking for.

jinksys · 03-16-2004, 03:07 AM

Quote:

Originally posted by hypexr
I think that gcc filename 2>/mnt/floppy/error_log might be what you are looking for.

For some reason hypexr, that doesnt work with GCC. It seems it doesnt send errors to
STDERR, (at least it doesnt on my machine) thats why I used &> to send all messages to error since gcc usually only whines when something blows up.

hypexr · 03-16-2004, 12:53 PM

Works on my system, but thanks, thats good information to know.

xviddivxoggmp3 · 03-16-2004, 03:38 PM

To expand on this concept.
I'm assuming that you can send this to a mounted network drive?
Is this valid?
I do not have the capability of testing this, so I do appologize for the question.
What about across the internet on a remote machine?