public inbox for
 help / color / mirror / Atom feed
From: Ross Johnson <>
Subject: Re: unexpected end of file :-(
Date: Wed, 03 Nov 2004 01:38:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Bastian,

There haven't been any other reports of this problem. Are 
you using a snapshot version of the pthreads-win32 library, 
or a version out of CVS?

One other thing I notice though - you said that when you 
#define all the pthread functions that you use it works, but 
you have defined
#define pthread_cleanup_push(a,b)
and no
#define pthread_cleanup_pop(a)

Is that an omission? The way these are defined is as a pair 
that forms the start and end of a block. That is, push with 
no pop will create an unbalanced { ... }, and that could be 
the problem.


Bastian Voigt wrote:

> Hello List!
> I am working with pthreads-win32 and the microsoft vc++ compiler 
> version 6.
> I have a problem I already spent hours on:
> I have ported a source file which was perfectly working before, to run 
> in an own pthread.
> Now the compiler always bitches about "unexpected end of file" (fatal 
> error C1004).
> On the following MSDN library page a verbose error description can be 
> found:
> - When I comment out all the pthreads related function calls and the 
> #include pthreads statement,
> then the file compiles perfectly. And yes, I am pretty sure that those 
> lines are syntactically correct.
> - When all the used pthread_* functions are defined as macros the file 
> also compiles perfectly:
> //#include <pthread.h>   #define pthread_setcancelstate(a, b)
> #define pthread_cleanup_push(a,b)
> #define pthread_exit(a)
> So it appears to me that the problem must lie somewhere inside 
> pthread.h ?
> BTW my project also includes the IBM SCC libraries
> (see
> I have managed to compile and run a little pthreads example program, 
> but that was without SCC library import...
> Any thoughts on this matter highly appreciated..
> Greetings
> Bastian Voigt

  reply	other threads:[~2004-11-03  1:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02  9:59 Bastian Voigt
2004-11-03  1:38 ` Ross Johnson [this message]
     [not found] ` <>
2004-11-03 10:50   ` Bastian Voigt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).