embedded server for 4.1.9

------=_NextPart_000_0050_01C50932.533B57E0
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_0051_01C50932.533B57E0"


------=_NextPart_001_0051_01C50932.533B57E0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit



I had written a windows app using the C api that used the embedded
server for 4.0.18, and it worked fine. Now I am trying to upgrade to
4.1.9, and it is not working. When I hit the statement
mysql_real_connect, it gpf's. This behaviour is the same as what I
experience when I try to run the original app built for 4.0.18 against a
db that was built with 4.1.9.

Any ideas?




------=_NextPart_001_0051_01C50932.533B57E0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable




charset=3Dus-ascii">









lang=3DEN-US
link=3D"#0066CC" vlink=3D"#999999">

Re: embedded server for 4.1.9

--=_alternative 0070278085256F9C_=
Content-Type: text/plain; charset="US-ASCII"

"Joseph Garry" wrote on 02/02/2005 03:20:19 PM:

>
> I had written a windows app using the C api that used the embedded
> server for 4.0.18, and it worked fine. Now I am trying to upgrade to
> 4.1.9, and it is not working. When I hit the statement
> mysql_real_connect, it gpf's. This behaviour is the same as what I
> experience when I try to run the original app built for 4.0.18
> against a db that was built with 4.1.9.
> Any ideas?
>

I can't tell you why it's gpf-ing but have to ask if you factored in the
change in authentication methods that happened at version 4.1 into your
design? You are all around that breaking point (working in both
directions). There is a lot of information on that change in the manual
and in this list's archive. Just my $.02

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine
--=_alternative 0070278085256F9C_=--

RE: embedded server for 4.1.9

Thanks for your response. From what I read, this should be a problem if
you attempt to connect a client built with earlier versions of the
client libraries with a db built with 4.1.9. But in this case I have
rebuilt the app with the client libraries for 4.1.9. Also, the app
gpf's. If it were an authentication issue, I would expect that it would
simply fail to connect. As well, I have downloaded the source for 4.1.9,
and have tried to run the test for the embedded server, and I am getting
similar results. Hmmmm.

Joe Garry
Software Engineer
US Biometrics


-----Original Message-----
From: SGreen@unimin.com [mailto:SGreen@unimin.com]
Sent: Wednesday, February 02, 2005 2:22 PM
To: Joe Garry
Cc: win32@lists.mysql.com
Subject: Re: embedded server for 4.1.9

"Joseph Garry" wrote on 02/02/2005 03:20:19
PM:

>
> I had written a windows app using the C api that used the embedded
> server for 4.0.18, and it worked fine. Now I am trying to upgrade to
> 4.1.9, and it is not working. When I hit the statement
> mysql_real_connect, it gpf's. This behaviour is the same as what I
> experience when I try to run the original app built for 4.0.18
> against a db that was built with 4.1.9.
> Any ideas?
>

I can't tell you why it's gpf-ing but have to ask if you factored in the

change in authentication methods that happened at version 4.1 into your
design? You are all around that breaking point (working in both
directions). There is a lot of information on that change in the manual

and in this list's archive. Just my $.02

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

RE: embedded server for 4.1.9

--=_alternative 0079E57285256F9C_=
Content-Type: text/plain; charset="US-ASCII"

Yep, you seem to have a good handle on the authentication issue. Have you
tried compiling a DEBUG version and tracing through the code? Maybe you
can catch the GPF when it happens and figure out what's messing up. Since
it's failing early (during a connection) this should be rather easy to
capture and debug.

I don't know how many people on this list actually compile their own
servers let alone deal with the embedded version. You may have better luck
with someone on the GENERAL discussion list. (I CC:ed that list with my
response)

Sorry, but compiling/building MySQL is not something I have done yet, I
defer to all the others with more experience. I am sure someone can help
you run this fault to ground. ;-)

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine


"Joseph Garry" wrote on 02/02/2005 04:00:25 PM:

> Thanks for your response. From what I read, this should be a problem if
> you attempt to connect a client built with earlier versions of the
> client libraries with a db built with 4.1.9. But in this case I have
> rebuilt the app with the client libraries for 4.1.9. Also, the app
> gpf's. If it were an authentication issue, I would expect that it would
> simply fail to connect. As well, I have downloaded the source for 4.1.9,
> and have tried to run the test for the embedded server, and I am getting
> similar results. Hmmmm.
>
> Joe Garry
> Software Engineer
> US Biometrics
>
>
> -----Original Message-----
> From: SGreen@unimin.com [mailto:SGreen@unimin.com]
> Sent: Wednesday, February 02, 2005 2:22 PM
> To: Joe Garry
> Cc: win32@lists.mysql.com
> Subject: Re: embedded server for 4.1.9
>
> "Joseph Garry" wrote on 02/02/2005 03:20:19
> PM:
>
> >
> > I had written a windows app using the C api that used the embedded
> > server for 4.0.18, and it worked fine. Now I am trying to upgrade to
> > 4.1.9, and it is not working. When I hit the statement
> > mysql_real_connect, it gpf's. This behaviour is the same as what I
> > experience when I try to run the original app built for 4.0.18
> > against a db that was built with 4.1.9.
> > Any ideas?
> >
>
> I can't tell you why it's gpf-ing but have to ask if you factored in the
>
> change in authentication methods that happened at version 4.1 into your
> design? You are all around that breaking point (working in both
> directions). There is a lot of information on that change in the manual
>
> and in this list's archive. Just my $.02
>
> Shawn Green
> Database Administrator
> Unimin Corporation - Spruce Pine
>

--=_alternative 0079E57285256F9C_=--

RE: embedded server for 4.1.9

I put something out on the general forum. Perhaps I could try the
general list. Thanks for your help.

=20

Joe Garry

Software Engineer=20

US Biometrics

=20

-----Original Message-----
From: SGreen@unimin.com [mailto:SGreen@unimin.com]=20
Sent: Wednesday, February 02, 2005 4:09 PM
To: Joe Garry
Cc: win32@lists.mysql.com; mysql@lists.mysql.com
Subject: RE: embedded server for 4.1.9

=20


Yep, you seem to have a good handle on the authentication issue. Have
you tried compiling a DEBUG version and tracing through the code? Maybe
you can catch the GPF when it happens and figure out what's messing up.
Since it's failing early (during a connection) this should be rather
easy to capture and debug.=20

I don't know how many people on this list actually compile their own
servers let alone deal with the embedded version. You may have better
luck with someone on the GENERAL discussion list. (I CC:ed that list
with my response)=20

Sorry, but compiling/building MySQL is not something I have done yet, I
defer to all the others with more experience. I am sure someone can help
you run this fault to ground. ;-)=20

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine=20


"Joseph Garry" wrote on 02/02/2005 04:00:25
PM:

> Thanks for your response. From what I read, this should be a problem
if
> you attempt to connect a client built with earlier versions of the
> client libraries with a db built with 4.1.9. But in this case I have
> rebuilt the app with the client libraries for 4.1.9. Also, the app
> gpf's. If it were an authentication issue, I would expect that it
would
> simply fail to connect. As well, I have downloaded the source for
4.1.9,
> and have tried to run the test for the embedded server, and I am
getting
> similar results. Hmmmm.
>=20
> Joe Garry
> Software Engineer=20
> US Biometrics
>=20
>=20
> -----Original Message-----
> From: SGreen@unimin.com [mailto:SGreen@unimin.com]=20
> Sent: Wednesday, February 02, 2005 2:22 PM
> To: Joe Garry
> Cc: win32@lists.mysql.com
> Subject: Re: embedded server for 4.1.9
>=20
> "Joseph Garry" wrote on 02/02/2005 03:20:19
> PM:
>=20
> >=20
> > I had written a windows app using the C api that used the embedded=20
> > server for 4.0.18, and it worked fine. Now I am trying to upgrade to
> > 4.1.9, and it is not working. When I hit the statement=20
> > mysql_real_connect, it gpf's. This behaviour is the same as what I=20
> > experience when I try to run the original app built for 4.0.18=20
> > against a db that was built with 4.1.9.
> > Any ideas?
> >=20
>=20
> I can't tell you why it's gpf-ing but have to ask if you factored in
the
>=20
> change in authentication methods that happened at version 4.1 into
your=20
> design? You are all around that breaking point (working in both=20
> directions). There is a lot of information on that change in the
manual
>=20
> and in this list's archive. Just my $.02
>=20
> Shawn Green
> Database Administrator
> Unimin Corporation - Spruce Pine
>=20


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org