[fdo-dev] [fdordbms] UnitTest segmentation fault

Romica Dascalescu Romica.Dascalescu at autodesk.com
Thu Oct 12 11:39:53 EDT 2006

Hi Mateusz,

I will fix the unit tests by changing UnitTestUtil::GetEnviron() to
return "" and not NULL.

You will be able to send an empty password by:
 - Using a string like service=mysqlserver;username=root;password=;
 - Not setting the password in init file e.g.
The default value for password is "".

There is no rule to fill up these parameters. If you want to be able to
connect to a server you must set the data which the server needs (at
least service and username) otherwise the connection will fail.
The parameters from initfiletest take set values or if missing take the
default values.
As main rule is better to consider all parameters are required.


-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net] 
Sent: Thursday, October 12, 2006 10:47 AM
To: dev at fdo.osgeo.org
Subject: Re: [fdo-dev] [fdordbms] UnitTest segmentation fault


As my initial questions in this thread seem to be unanswerable or
unclear, I'd like to give it yet another try.

Could you answer following short questions?

1. Are parameters used in the initfiletest file validated in any way?

2. What parameters are mandatory what are optional?

3. How to pass empty password?
As I explained in my first post in this thread, following
versions do not work:

(not password parameter)
password="" - this one seems to be working but I'm not sure.

4. Why pointer returned from getenv(), and from other C lib calls,
are not checked for NULL?

Mateusz Loskot

To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
For additional commands, e-mail: dev-help at fdo.osgeo.org

More information about the Fdo-internals mailing list