On 6-6-2010 19:06, Jim wrote:
> On 6-6-2010 16:06, Michael Van Canneyt wrote:
>>
>>
>> On Sun, 6 Jun 2010, Jim wrote:
>>> (gdb) break fpc_raiseexception
>>> Breakpoint 1 at 0x40a9c6
>>> .. debug output
>>> Breakpoint 1, 0x0040a9c6 in fpc_raiseexception ()
>>> (gdb) backtrace
>>> #0 0x0040a
On 6-6-2010 16:06, Michael Van Canneyt wrote:
>
>
> On Sun, 6 Jun 2010, Jim wrote:
>> (gdb) break fpc_raiseexception
>> Breakpoint 1 at 0x40a9c6
>> .. debug output
>> Breakpoint 1, 0x0040a9c6 in fpc_raiseexception ()
>> (gdb) backtrace
>> #0 0x0040a9c6 in fpc_raiseexception ()
>> #1 0x0
On Sun, 6 Jun 2010, Jim wrote:
(gdb) break fpc_raiseexception
Breakpoint 1 at 0x40a9c6
.. debug output
Breakpoint 1, 0x0040a9c6 in fpc_raiseexception ()
(gdb) backtrace
#0 0x0040a9c6 in fpc_raiseexception ()
#1 0x0043d284 in
IBCONNECTION_TIBCONNECTION_$__CHECKERROR$ANSISTRING$PISC_STA
On 5-6-2010 10:47, Michael Van Canneyt wrote:
> It might be worth putting all parameters in a record definition and pass
> the
> record to your function. That makes the procedure declaration somewhat more
> manageable and understandable. (and definitely more efficent as well).
Progress!
As you su
On 6-6-2010 11:54, Michael Van Canneyt wrote:
> Maybe there is some special handling required for firebird exceptions,
> although that would surprise me. Normally I'd simply expect this to
> be a special error code, and the message of the exception as the error
> message...
>
> Michael.
Found a pd
On 6-6-2010 11:54, Michael Van Canneyt wrote:
> On Sun, 6 Jun 2010, Jim wrote:
>> On 5-6-2010 12:23, Michael Van Canneyt wrote:
>>> On Sat, 5 Jun 2010, Jim wrote:
On 5-6-2010 10:47, Michael Van Canneyt wrote:
> On Sat, 5 Jun 2010, Jim wrote:
>
> Is the firebird UDF written in fpc ?
On Sun, 6 Jun 2010, Jim wrote:
On 5-6-2010 12:23, Michael Van Canneyt wrote:
On Sat, 5 Jun 2010, Jim wrote:
On 5-6-2010 10:47, Michael Van Canneyt wrote:
On Sat, 5 Jun 2010, Jim wrote:
Program received signal SIGSEGV, Segmentation fault.
0x0001ad7d in FINALIZE$_DATEUTILS ()
(gdb)
On 5-6-2010 12:23, Michael Van Canneyt wrote:
> On Sat, 5 Jun 2010, Jim wrote:
>> On 5-6-2010 10:47, Michael Van Canneyt wrote:
>>> On Sat, 5 Jun 2010, Jim wrote:
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x0001ad7d in FINALIZE$_DATEUTILS ()
>> (gdb) backtrace
>> #0 0x
On Sat, 5 Jun 2010, Jim wrote:
On 5-6-2010 10:47, Michael Van Canneyt wrote:
On Sat, 5 Jun 2010, Jim wrote:
Finally, the question:
What I really want is to get a Firebird SQLCODE error code or some other
details that allow me to figure out whether one of my custom exceptions
get called. Al
On 5-6-2010 10:47, Michael Van Canneyt wrote:
> On Sat, 5 Jun 2010, Jim wrote:
>> Finally, the question:
>> What I really want is to get a Firebird SQLCODE error code or some other
>> details that allow me to figure out whether one of my custom exceptions
>> get called. Also, it seems something is
On 5-6-2010 10:47, Michael Van Canneyt wrote:
> On Sat, 5 Jun 2010, Jim wrote:
>> Finally, the question:
>> What I really want is to get a Firebird SQLCODE error code or some other
>> details that allow me to figure out whether one of my custom exceptions
>> get called. Also, it seems something is
On Sat, 5 Jun 2010, Jim wrote:
Hi all,
Still working on my locate clone at
http://bitbucket.org/jb/flocate/
- download at
http://bitbucket.org/jb/flocate/downloads
Running Free Pascal Compiler version 2.4.1 [2010/06/01] for x86_64 on
Windows.
I've cobbled together some Firebird database cod
Hi all,
Still working on my locate clone at
http://bitbucket.org/jb/flocate/
- download at
http://bitbucket.org/jb/flocate/downloads
Running Free Pascal Compiler version 2.4.1 [2010/06/01] for x86_64 on
Windows.
I've cobbled together some Firebird database code.
If you want to have a more comple
13 matches
Mail list logo
