delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/05/08/04:00:57

From: leetonks AT hotmail DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP 2.01 spawnvp problem......
Date: Fri, 08 May 1998 07:42:23 GMT
Organization: Deja News - The Leader in Internet Discussion
Lines: 63
Message-ID: <6iud0u$h33$1@nnrp1.dejanews.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980507164610 DOT 6703D-100000 AT is>
Reply-To: l DOT tonks AT no DOT spam DOT please DOT pindar DOT com
NNTP-Posting-Host: 194.193.96.250
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <Pine DOT SUN DOT 3 DOT 91 DOT 980507164610 DOT 6703D-100000 AT is>,
  Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
>
>
> On Thu, 7 May 1998 leetonks AT hotmail DOT com wrote:
>
> Did you remember to make prog the first element of par as well?  This is
> by far the most frequent problem with using spawnXX functions.

I did, yes. Although I didn't at first - it was never mentioned in the info
for the spawn series of commands and I only happened upon the information
while looking for clues as to why it wasn't working. It didn't help. :-(


> par[0] should be the same string as prog, or it won't work.  Also, the
> last member of par[] should be a NULL pointer.

And that was the problem! I didn't know I should be passing a NULL pointer at
the end of the args list - the code works perfectly now. THANKS!

Again, this isn't mentioned in the docs. Any other shortcomings I should know
about? ;-)


> I think you are mixing the error code associated with the SIGSEGV
> exception and error code of file operations.  When SIGSEGV prints error
> code 4, it means that you are accessing memory using illegal pointer or
> address.  The DJGPP FAQ explains how to convert the crash traceback into
> human-readable info in section 9.2 (the FAQ is available as
> v2/faq210b.zip from the same place you get DJGPP).  After this
> conversion, you should be able to see where in your code does it blow up,
> which makes debugging easier.

Yes I was, sorry. After reading the FAQ section you mention again I understand
more about the traceback... perhaps next time I might be able to figure it out
for myself!


> Also, please note that for efficient help, it is advisable to post the
> entire stack traceback printed when your program crashes (after passing
> it through `symify', see the above-mentioned section of the FAQ).

Understood. I'll remember that for future problems.


> DJGPP supports up to 255 open files, limited only by the value of FILES=
> directive on your CONFIG.SYS.  You don't need to recompile the library,
> this feature is enabled by default.  Whoever submitted that report to the
> bug-tracker was dead wrong.

Whoops - and there's me thinking the bug-tracker only included valid info!


Thanks for all your help - very much appreciated!



Lee.



-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/   Now offering spam-free web-based newsreading

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019