Re: FW: New user of mdbtools

"Nigel Kendrick" <[email protected]> writes:

> Glad there's some life here!!
>
> I'll submit the code and see what happens.
>
> Things have been working fine until I tried to generate a csv file from a
> large table containing a lot of text fields -  mdb-export crashes out with:
>
> *** glibc detected *** /usr/local/bin/.libs/lt-mdb-export: double free or
> corruption (out): 0x08f0dcb0 *** 
>
> I cannot see any problems in the Access table that could cause some kind of
> error condition but the export stops at exactly the same record every time
> and suspiciously close to when it creates a 100MB csv file (104140795) so
> could I be hitting a memory allocation limit or am I totally off-the-mark? 

Could be... Hard to tell, but I don't think so...

I have looked at you patch...

You do know that your "-L" is only active when you do not also specify "-Q",
right?

I cannot see any obvious errors in your code.

It's time for debugging: valgrind, gdb.

Anyway: I think it is a much cleaner solution to post-process your
generated SQL (using awk) to produce the output needed; thereby
seperating the two responsibilities: DB conversion and Data manipulation.

Jarl


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php