Re: [mdb-dev] Segfault reading JET3 mdb (cont.)

[Petro V. <Pe...@nc...>]

On Mon, 02 Feb 2004 09:44:09 +0000
Will Newton <wi...@gb...> wrote:

> 
> The patch is really attached this time (good old Monday morning).
> 
> Heres some additional debugging output from reading memo fields:
> 
> Reading LVAL page 000001
> offset 926943232 is beyond EOF
> Reading LVAL page 028f72
> offset 343642112 is beyond EOF
> Reading LVAL page 000009
> offset 776472576 is beyond EOF
> Reading LVAL page 001770
> Reading LVAL page 100040
> offset 532154368 is beyond EOF
> Reading LVAL page 028f72
> offset 343642112 is beyond EOF
> Reading LVAL page 654d20
> offset 711524352 is beyond EOF
> 
> The wildly fluctuating values of lval_pg seem a bit odd to
> me.
> 

Hi, I've used your patch on the source I got from CVS a couple of days ago.
However, I am getting this error:

# isql MSAccess
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL> select * from ctx
isql: relocation error: /usr/lib/libmdbodbc.so: undefined symbol: mdb_crack_row
# 

The interesting bit is that i can browse the tables in the database throught
gmdb2. The data shows up. When i try to run a query gmdb2 segfaults.

Any ideas?


--
Petro