mdbtools-dev

Re: [mdb-dev] Segfault when listing tables and problemsexportingtables

[Matt R. <mre...@te...>]

On Mon, 2004-06-14 at 12:35, David Mansfield wrote:
> I don't know.  I just tried and got everything working with these exact
> commands on a Fedora Core 2 system.  I developed the patches on Red Hat
> 9 and have deployed successfully on Red Hat 7.2 and 7.3 and RHEL 3 as
> well.  Not sure what your exact problem is.  Can you try this exactly:
>=20
> (assumes patch in ~/patches, and your mdb file in ~)
>=20
> mkdir tmp=20
> cd tmp=20
> wget http://download.sourceforge.net/mdbtools/mdbtools-0.5.tar.gz
> tar xvzf mdbtools-0.5.tar.gz=20
> cd mdbtools-0.5=20
> patch -p1 <~/patches/mdbtools-combined.patch=20
> ./configure --prefix=3D/usr/local/mdbtools=20
> make=20
> make install=20
> /usr/local/mdbtools/bin/mdb-schema ~/05260930_orlando.mdb
> /usr/local/mdbtools/bin/mdb-export 05260930_orlando.mdb \
> 	QcpCdma1xActiveSetInfo_XXX
>=20
> Works for me.
>=20
> Can you cut and paste the error if you still get it?
>=20
> David

I found it.  When I ran configure, lex/bison weren't installed and
configure didn't include them later.

So yes, this runs fine now I think.
--=20
Matt Reynolds <mre...@te...>

Re: [mdb-dev] Segfault when listing tables and problemsexportingtables

[Matt R. <mre...@te...>]

On Mon, 2004-06-14 at 12:35, David Mansfield wrote:
> On Mon, 2004-06-14 at 14:58, Matt Reynolds wrote:
> /usr/local/mdbtools/bin/mdb-export 05260930_orlando.mdb \
> 	QcpCdma1xActiveSetInfo_XXX
>=20

Actually, I think I lied.  This does work, but isn't the table I want to
dump.

This command:
mdb-export 05260930_orlando.mdb \ QcpCDMA1xRadioLinkProtocolStats_XXX

Still doesn't output anything.

So, looking into it a bit more, I realized that mdb-tables isn't dumping
the table I'm interested in.  It shows :
QcpCdma1xRevPwrCtrl_XXX_FltStats QcpCdma1xRadioLinkProtocolStats
QcpCdma1xRadioLinkProtocolStats_ QcpCdma1xRadioLinkProtocolStats_
QcpCdma1xRadioLinkProtocolStats_

Those last three tables are supposed to be :
QcpCdma1xRadioLinkProtocolStats_XXX
QcpCdma1xRadioLinkProtocolStats_XXX_IntBest
QcpCdma1xRadioLinkProtocolStats_XXX_UI4$I2

I think that's why I can't dump them.  Any idea why these tables aren't
being dumped?

--=20
Matt Reynolds <mre...@te...>

Re: [mdb-dev] Segfault when listing tables and problemsexportingtables

[David M. <da...@co...>]

On Mon, 2004-06-14 at 16:06, Matt Reynolds wrote:
> On Mon, 2004-06-14 at 12:35, David Mansfield wrote:
> > On Mon, 2004-06-14 at 14:58, Matt Reynolds wrote:
> > /usr/local/mdbtools/bin/mdb-export 05260930_orlando.mdb \
> > 	QcpCdma1xActiveSetInfo_XXX
> > 
> 
> Actually, I think I lied.  This does work, but isn't the table I want to
> dump.
> 
> This command:
> mdb-export 05260930_orlando.mdb \ QcpCDMA1xRadioLinkProtocolStats_XXX
> 
> Still doesn't output anything.
> 
> So, looking into it a bit more, I realized that mdb-tables isn't dumping
> the table I'm interested in.  It shows :
> QcpCdma1xRevPwrCtrl_XXX_FltStats QcpCdma1xRadioLinkProtocolStats
> QcpCdma1xRadioLinkProtocolStats_ QcpCdma1xRadioLinkProtocolStats_
> QcpCdma1xRadioLinkProtocolStats_
> 
> Those last three tables are supposed to be :
> QcpCdma1xRadioLinkProtocolStats_XXX
> QcpCdma1xRadioLinkProtocolStats_XXX_IntBest
> QcpCdma1xRadioLinkProtocolStats_XXX_UI4$I2
> 
> I think that's why I can't dump them.  Any idea why these tables aren't
> being dumped?

Hmm. You're right.  There's something really funky going on.  If  you
look closely at the output of mdb-tables, or mdb-schema, there are some
'unprintable' characters being generated as part of the table name for
some tables, including these.

So the table name is not being extracted correctly.  That's probably a
bug somewhere...  Possibly in the unicode string extraction or
something.

Let's see... Ok.  It seems as though the 'hardcoded' max object name
length of 30 is screwing you up.  If we hardcode it to 50 it works. 
(begs a different question but....).  So try the attached patch on top
of the combined patch and it seems to work.

NOTE: the table names ARE case sensitive, so be sure to use mdb-tables
to get the exact name, then cut-and-paste for mdb-export.

David

RE: [mdb-dev] Segfault when listing tables andproblemsexportingtables

[Fergus A. <f_W...@ya...>]

As a design point, table names should only be case sensitive when
delimited

Thus:

Select * from tbl_Neo
Select * from TBL_NEO

Are identical, but 


Select * from "tbl_Neo"
Select * from "TBL_NEO"

Are different. Example assumes double quote is the delimiter character.

Regards

Fergus Allan



-----Original Message-----
From: mdb...@li...
[mailto:mdb...@li...] On Behalf Of David
Mansfield
Sent: 14 June 2004 22:06
To: Matt Reynolds
Cc: MDB Tools List
Subject: Re: [mdb-dev] Segfault when listing tables
andproblemsexportingtables

On Mon, 2004-06-14 at 16:06, Matt Reynolds wrote:
> On Mon, 2004-06-14 at 12:35, David Mansfield wrote:
> > On Mon, 2004-06-14 at 14:58, Matt Reynolds wrote:
> > /usr/local/mdbtools/bin/mdb-export 05260930_orlando.mdb \
> > 	QcpCdma1xActiveSetInfo_XXX
> > 
> 
> Actually, I think I lied.  This does work, but isn't the table I want
to
> dump.
> 
> This command:
> mdb-export 05260930_orlando.mdb \ QcpCDMA1xRadioLinkProtocolStats_XXX
> 
> Still doesn't output anything.
> 
> So, looking into it a bit more, I realized that mdb-tables isn't
dumping
> the table I'm interested in.  It shows :
> QcpCdma1xRevPwrCtrl_XXX_FltStats QcpCdma1xRadioLinkProtocolStats
> QcpCdma1xRadioLinkProtocolStats_ QcpCdma1xRadioLinkProtocolStats_
> QcpCdma1xRadioLinkProtocolStats_
> 
> Those last three tables are supposed to be :
> QcpCdma1xRadioLinkProtocolStats_XXX
> QcpCdma1xRadioLinkProtocolStats_XXX_IntBest
> QcpCdma1xRadioLinkProtocolStats_XXX_UI4$I2
> 
> I think that's why I can't dump them.  Any idea why these tables
aren't
> being dumped?

Hmm. You're right.  There's something really funky going on.  If  you
look closely at the output of mdb-tables, or mdb-schema, there are some
'unprintable' characters being generated as part of the table name for
some tables, including these.

So the table name is not being extracted correctly.  That's probably a
bug somewhere...  Possibly in the unicode string extraction or
something.

Let's see... Ok.  It seems as though the 'hardcoded' max object name
length of 30 is screwing you up.  If we hardcode it to 50 it works. 
(begs a different question but....).  So try the attached patch on top
of the combined patch and it seems to work.

NOTE: the table names ARE case sensitive, so be sure to use mdb-tables
to get the exact name, then cut-and-paste for mdb-export.

David