hi andrzej, 

run00169564_express0_hicollisions job of tct with 17.0.x.y crashes in esdtodpd step. 
https://atlasrtt.cern.ch/tct/rel_2/17.0.x.y/build/i686-slc5-gcc43-opt/offline/tier0chaintests/run00169564_express0_hicollisions/run00169564_express0_hicollisions_log
+verbatim+
level-1 configuration database version 3.1 atlas q_initial read.
contains 12 trigger sector types:
negative sectors  0 - 15 ==&gt;  1  2  2  3  3  2  2  4  4  2  2  1  1  5  5  6 
negative sectors 16 - 31 ==&gt;  6  2  2  6  6  7  7  8  8  7  7  6  6  2  2  1 
positive sectors 32 - 47 ==&gt;  9  2  2  9  9  2  2 10 10  2  2  1  1  5  5  1 
positive sectors 48 - 63 ==&gt;  1  2  2  6  6 12 12 11 11 12 12  6  6  2  2  9 

classidsvc                                           info  getregistryentries: read 22932 clidregistry entries for module all
py:esdtodpd          info esdtodpd has completed running of athena with exit code -11.
py:esdtodpd         error athena received signal 11. exit code reset to athena exit code 8.
athenalogchecker start [esdtodpd log] wall-time: tue aug 09 17:57:39 2011 cest, vmem: 110.1015625 mb, rss: 71.52734375 mb
py:esdtodpd          info scanning athena logfile esdtodpd.log assuming atlas release all,rel_2 ...
-verbatim-

+verbatim+
stage_svcclass=atlcal 
tct_recotrf.py --hi --jobnum=0 --ami=q202 --nfiles=3 --maxevents=250 --trigstream=express --runnum=00169564 --preinclude=recjobtransforms/heavyiondatarecconfig.py --castordir=/castor/cern.ch/grid/atlas/ero/prod1/perm/data10_hi/express_express/0169564/data10_hi.00169564.express_express.merge.raw --lumiblock=405,407
-verbatim-
reproduces the crash. 
--maxevents=25 was ok but --maxevents=80 was not ok. 

please have a look. 

cheers, 
susumu 