FW: New user of mdbtools

[Nigel kendrick]

-----Original Message-----
From: Jarl Friis [mailto:jarl@...]
Sent: Monday, June 23, 2008 12:09 PM
To: Nigel Kendrick
Cc: mdbtools-dev@...
Subject: Re: [mdb-dev] New user of mdbtools

[Snip]

I will suggest that you do like the rest of us...
Submit a patch on
http://sourceforge.net/tracker/?group_id=2294&atid=302294

I can reccomend
Patch for UTF-8
Patch for export to SQLite

:-)

When you have done that, you can post a mail here on the list.

Jarl




Hi Jarl,

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?

I'm afraid I am only 2-days 'into' c programming so I wouldn't know where to
start looking!?

Thanks

Nigel


EDIT:

Apologies to Jarl - my first reply went direct and not to the list.

Scrap the idea of the 100MB limit as one of my exports to csv makes it to
177MB without any problems.


-------------------------------------------------------------------------
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
_______________________________________________
mdbtools-dev mailing list
mdbtools-dev@...
https://lists.sourceforge.net/lists/listinfo/mdbtools-dev

[Jarl Friis-2]

"Nigel Kendrick" <support-lists@...> 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
_______________________________________________
mdbtools-dev mailing list
mdbtools-dev@...
https://lists.sourceforge.net/lists/listinfo/mdbtools-dev

[Nigel kendrick]

> 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

Thanks for the feedback - the export runs if I remove two rows/records in
the database so it looks like there is a small corruption which I can easily
fix. Not sure if its worth the time to find out what's tripping the export
and make sure its trapped as the problem only occurs with 1 table out of 25
I am exporting.

Thanks also for the comments on my first ever 'c' coding!

Nigel


-------------------------------------------------------------------------
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
_______________________________________________
mdbtools-dev mailing list
mdbtools-dev@...
https://lists.sourceforge.net/lists/listinfo/mdbtools-dev