Hi, it compiled correctly but i still can't get debug infoI tried to be a smartass and make clean all with OPT=-gl but of course it failed!the closest i got to the error is in ibconnection.pp file"procedure TIBConnection.Execute(cursor: TSQLCursor;atransaction:tSQLtransaction; AParams : TParams);var tr : pointer;? ? out_SQLDA : PXSQLDA;begin? tr := aTransaction.Handle;? if Assigned(APArams) and (AParams.count > 0) then SetParameters(cursor, atransaction, AParams);? with cursor as TIBCursor do? begin? ? if FStatementType = stExecProcedure then? ? ? out_SQLDA := SQLDA? ? else? ? ? out_SQLDA := nil;? ? if isc_dsql_execute2(@Status[0], @tr, @Statement, 1, in_SQLDA, out_SQLDA) 0 then? ? ? CheckError('Execute', Status);? end;end;"where i guess one of the pointers fail.My problem is that i don't know the exact line of the error, i have a snapshot of my screen but i can't send it to the list because of the size limits
On Saturday, November 8, 2014 6:28 PM, Chris Rempas wrote:
Hi, it compiled correctly but i still can't get debug infoI tried to be a smartass and make clean all with OPT=-gl but of course it failed!the closest i got to the error is in ibconnection.pp file"procedure TIBConnection.Execute(cursor: TSQLCursor;atransaction:tSQLtransaction; AParams : TParams);var tr : pointer;? ? out_SQLDA : PXSQLDA;begin? tr := aTransaction.Handle;? if Assigned(APArams) and (AParams.count > 0) then SetParameters(cursor, atransaction, AParams);? with cursor as TIBCursor do? begin? ? if FStatementType = stExecProcedure then? ? ? out_SQLDA := SQLDA? ? else? ? ? out_SQLDA := nil;? ? if isc_dsql_execute2(@Status[0], @tr, @Statement, 1, in_SQLDA, out_SQLDA) 0 then? ? ? CheckError('Execute', Status);? end;end;" where i guess one of the pointers fail.My problem is that i don't know the exact line of the error, i have a snapshot of my screen but i can't send it to the list because of the size limits
On Friday, November 7, 2014 7:24 PM, Joost van der Sluis wrote:Chris Rempas wrote 6 lines
That's really strange. Here it works, and also the testsuite has some tests for this.
What you could do is build fcl-db with debug-info. Search for the fcl-db sources (packages/fcl-db). Open a command-line (powershell) and make fcl-db the current directory. Then do 'make clean all OPT=-gl'. And then do 'make install'. Note that it could be that you have to run pwoershell as administrator to be able to do a 'make install'.
Now rebuild your application and try again. Now you should be able to see where the problem arises, and get some more information using the debugger.
Regards,
Joost.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20141108/2c604b36/attachment.html>
