logging-log4cxx-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale King" <dalewk...@gmail.com>
Subject Re: 2 issues found with 0.10.0-RC2
Date Sat, 08 Mar 2008 20:24:09 GMT
It failed at compile time.

For windows at least with unicode these names are actually #defines of the form:

#define SQLExecDirect SQLExecDirectW

I was trying to find some way with a #if to ask the question like:

#if SQLExecDirect == "SQLExecDirectW"

but there doesn't seem to be a way to do a conditional off of what
text is in a define.

I found another issue.

Started app with a TelnetAdapter, connected to it, closed connection,
reconfigure (automatically based on watchdog on the xml file), connect
again, app crashes. Seems to be very repeatable following those steps.

On Sat, Mar 8, 2008 at 1:03 PM, Curt Arnold <carnold@apache.org> wrote:
>  On Mar 6, 2008, at 4:27 PM, Dale King wrote:
>  > I built using visual studio and ran into a couple of problems to
>  > report.
>  >
>  > OdbcAppender  has unicode issues. There are 3 calls to SQL
>  > (SQLExecDirect, SQLDiagRec, and SQLDriverConnect) where the paramters
>  > are based on SQLCHAR. This doesn't work when building for Unicode as
>  > these functions really call the wide character version. Thes calls
>  > should have an A appended to the name to call the non unicode version.
>  > In reality this file should probably be made to work either way.
>  >
>  > I used a properties file and configured a ConsoleAppender but did not
>  > set the layout for it. Instead of nicely handling it, it crashed the
>  > application. Probably should fail more gracefully.
>  >
>  > --
>  > Dale King
>  Filed these as LOGCXX-248 and 249.  Will have to dig into the
>  ODBCAppender since that is also supported on Linux (using iODBC or
>  unixODBC) and just appending an "A" for the char-based API won't cover
>  that case.  How did it fail, at compile time or run time?

Dale King

View raw message