Re: [Quickfix-developers] Application crash when receiving logon message

[Caleb E. <cal...@gm...>]

On 6/6/05, Jose Moreno <jos...@db...> wrote:

> I don't think I am catching that error and that's why is probably being r=
aised all the way up the stack.

Actually, I think this error should be handled automatically by the QF
Session class, so I'm not sure why you're seeing a crash.  Unless
perhaps you've compiled your app or QuickFIX without exception
support?  Internally, the DataDictionary should throw a RepeatedTag
exception, but this should be caught by the calling code in
Session::next

It might be helpful to try running under the debugger or send along
some code samples so we can see what you're doing in your app.

> I haven't had the time to look into the internals of quickfix and I am no=
t sure where to put the error handler for this error.  Isn't it being raise=
d by a separate thread that reads messages from the TCP port?  I am not get=
ting a call into fromApp as I did put some trace messages there.

I think this exception should be dealt with internally by QuickFIX,
and yes it would be in the thread of your SocketConnection (separate
thread with ThreadedSocketConnection, main thread with the un-threaded
ver)..  In the case of a Logon message though, it should arrive at
your fromAdmin callback, not fromApp.

> On a related issue, I tried compiling quickfix with the callbacks enabled=
 but ,is it supposed to create a file with the call stack at the point of t=
he crash?  I haven't been able to find out where the output is for this.

I've never used the QF callstack stuff so I'm not sure where/how you'd
get data out of it.

--=20
Caleb Epstein
caleb dot epstein at gmail dot com