actually I don't quite understand how to read dtruss output, so I was
just guessing based on "readable" text of it. :-D
In case there's somebody would like to help me, here's the dstruss output...
simba:extpas bee$ sudo dtruss
/opt/local/apache2/cgi-bin/ExtPascalSamples.fcgi
SYSCALL(args)
I'm not sure what anyone can do for you except for trying to debug the
problem themselves. strace (or rather ktrace under Mac OS X 10.4.x, and
dtruss under Mac OS X 10.5.x) won't help at all if you indeed deleted
all units. You can also just as well look in the output of that as
anyone else to
On 27 Aug 2008, at 14:18, Bee wrote:
I'm on MacOS X 10.5.2 Intel. I got FPC 2.3.1 (SVN) and 2.2.2
installed. I'd like to revert my local SVN to the working revision,
but I forget which revision I should refer.
I had updated my svn, both for fpc and extpascal, to revision that
I'm sure it
I'm on MacOS X 10.5.2 Intel. I got FPC 2.3.1 (SVN) and 2.2.2 installed.
I'd like to revert my local SVN to the working revision, but I forget
which revision I should refer.
I had updated my svn, both for fpc and extpascal, to revision that I'm
sure it should work. It's based on the date of lat
Bee schrieb:
Find the last working revision using a binary search. Start e.g. with
rev. 11000: if works, try 11322 etc. With this scheme a handfull tests
give you the last working revision and we know which revision broke
things and needs to be fixed :) A small script could even automate this.
That is also the solution: make it public.
Ok, I made it public instead of published. FPC v.2.2.2 is able to
compile it. But, the problem with access violation still persists. :(
Anyway, thanks for the hint.
-Bee-
___
fpc-pascal maillist - fpc-p
In our previous episode, Bee said:
> >> be precise, FPC v.2.2.2 refuses an array of integer become data type
> >> for a published property.
>
> However, the fact that FPC v.2.2.2 raises the above error still bugs me.
> Is it by design? Because I read some reports that it worked with FPC
> v.2
Find the last working revision using a binary search. Start e.g. with
rev. 11000: if works, try 11322 etc. With this scheme a handfull tests
give you the last working revision and we know which revision broke
things and needs to be fixed :) A small script could even automate this.
Alright then
Bee schrieb:
Hi all,
I'm experimenting with ExtPascal (extpascal.googlecode.com). I used to
get it work using FPC 2.3.1 from SVN. Before today, my FPC SVN latest
update is about a month ago. Today, I update it.
Today FPC SVN is able to compile ExtPascal but the output is unusable.
It raises
Hi all,
I'm experimenting with ExtPascal (extpascal.googlecode.com). I used to
get it work using FPC 2.3.1 from SVN. Before today, my FPC SVN latest
update is about a month ago. Today, I update it.
Today FPC SVN is able to compile ExtPascal but the output is unusable.
It raises an access vio
10 matches
Mail list logo
