linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Kiehl <Holger.Kiehl@dwd.de>
To: gracecott@sancharnet.in
Cc: "Huber,
	George K RDECOM CERDEC STCD SRI" <George.K.Huber@us.army.mil>,
	linux-c-programming@vger.kernel.org
Subject: Re: problem in open sys call
Date: Wed, 21 Apr 2004 10:08:20 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0404211000250.1595@praktifix.dwd.de> (raw)
In-Reply-To: <40863A69.9090409@sancharnet.in>

On Wed, 21 Apr 2004, joy wrote:

> Huber, George K RDECOM CERDEC STCD SRI wrote:
> 
> >Hi,
> >
> >Try this:
> >
> >      if((fd=open(opcode, O_RDONLY))==-1)
> >      {
> >        printf("Open failed, error code: %d\n%s\n", errno, strerror(errno)
> >      }
> >      >you may need to add errno.h and string.h to the list of includes. This
> will
> >give you the error code and desctiption of why open is failing.
> >
> >
> thanks a lot, george but I think Glynn hit the nail on the head. the
> code was working fine before I added the opcode variable in main
> and totlly neglected to see it while gdb'ing.
> 
But George and others also made a good point. With programming it is always
good practice to write good error messages and always try to be more
verbose. Believe me this can save you a lot of time! I even go so far
to always print out __FILE__ and __LINE__, so I know exacly where the
error has happened.

Holger

  reply	other threads:[~2004-04-21 10:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 19:22 problem in open sys call Huber, George K RDECOM CERDEC STCD SRI
2004-04-21  9:10 ` joy
2004-04-21 10:08   ` Holger Kiehl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-20 18:31 joy
2004-04-20 20:06 ` Glynn Clements
2004-04-21  9:00   ` joy
2004-04-20 21:35 ` Steven Smith
2004-04-21  6:14 ` Vadiraj C S

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=Pine.LNX.4.58.0404211000250.1595@praktifix.dwd.de \
    --to=holger.kiehl@dwd.de \
    --cc=George.K.Huber@us.army.mil \
    --cc=gracecott@sancharnet.in \
    --cc=linux-c-programming@vger.kernel.org \
    /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 NNTP newsgroup(s).