|
Roland, I’ve seen crashing issues move from
5.0 ro 5.5 on Windows, so there really are no guarantees. That doesn’t
change the fact that 5.5 (especially on 10.4) seems to be a much better
solution. that said… The first thing you need to do is isolate
where in the TAF it’s crashing (if it’s always the same). You’re
best bet is to add either a file write action, email action, or a database
insert action between each major point of the TAF. You can start with just a
few, maybe even just one in the middle. But eventually you should (hopefully) be
able to isolate it down to a particular action. I would first try deleting that action and
recreating from scratch. There have been some discussions about TAF
corruption. Try searching for !CST, and look back through the WT list for more
info. If the TAF in question isn’t too
complex, you might just want to recreate it. Just don’t copy any code
over, just to be safe. Make sure you send all the crash info to
WT. You can ask them if there’s any hints to the problem. If the crash
info isn’t corrupted, they can usually see if it’s a TAF, TCF, datasource,
cache, etc. issue - although I make no guarantees here. Robert From: Roland Dumas
[mailto:[EMAIL PROTECTED] Have had this particular crash mode for a few months and not been able
to figure it out at all. It kills the witango log, so there is nothing there.
The crash happens when one application is hit, and occurs randomly. it might
occur 1 in 100 hits. What the taf is doing is just a few queries, nothing
fancy. the thread that crashes looks like this: Thread 23 Crashed: 0 witangod 0x00068ef8
0x1000 + 0x67ef8 1 witangod 0x000482a8
0x1000 + 0x472a8 2 witangod 0x00069cc4
0x1000 + 0x68cc4 3 witangod 0x0006b300
0x1000 + 0x6a300 4 witangod 0x00019bdc
0x1000 + 0x18bdc 5 witangod 0x0001a1d4
0x1000 + 0x191d4 6 witangod 0x00017e0c
0x1000 + 0x16e0c 7 witangod 0x0001ac90
0x1000 + 0x19c90 8 witangod 0x0014e7d8
0x1000 + 0x14d7d8 9 libSystem.B.dylib 0x90024910
_pthread_body + 0x28 any clues where to look for this. (pls don't say upgrade to 5.5. The client has not had enough trouble
free service from witango to be confident in another version.) Roland A. Dumas 310 650-347-1373 415-412-9300
(cell) AIM:
radumas
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf |
- Witango-Talk: crashing witango 5 on OS X Roland Dumas
- RE: Witango-Talk: crashing witango 5 on OS X Robert Shubert
- Re: Witango-Talk: crashing witango 5 on OS X Roland Dumas
- Re: Witango-Talk: crashing witango 5 on OS X Robert Garcia
- RE: Witango-Talk: crashing witango 5 on OS X Robert Shubert
- Re: Witango-Talk: crashing witango 5 on ... William M Conlon
- Re: Witango-Talk: crashing witango 5 on OS X William M Conlon
- Re: Witango-Talk: crashing witango 5 on ... Roland Dumas
- Re: Witango-Talk: crashing witango 5 on OS X William M Conlon
- Re: Witango-Talk: crashing witango 5 on OS X Roland Dumas
- Re: Witango-Talk: crashing witango 5 on OS X Roland Dumas
- Re: Witango-Talk: crashing witango 5 on OS X William M Conlon
