dag@ericsson.se (Dag von Arnold) (02/14/91)
If you reply by mail, please use the adress below. /Dag Return-Path: <ken@aom.ericsson.se> From: ken@aom.ericsson.se (Ken Sayers TM/U 62344 2396) Summary: We are looking for tools to help isolate erring code in a large OO sys Keywords: C++ debugging System We are developing large (100 thousand lines of code or more) systems using Sun's C++ compiler/debugger etc. We have some experience of developing and testing this type of system previously, but now that the size of the applications is growing, we feel we need something better that dbxtool to find the faulty unit, even at run time. We want to be able to guarantee that we can identify the actual method which is causing the problem or at least who we should hang. One way would be to trace all 'method activations, so that they could be analysed afterwards. Because of the volume of data in is clear that some restrictive form os trace would be desirable, or possibly an analysis program which could be run on large traces as an off-line job. Has anyone out there any experience of this type of problem? Are we missing something? We seem to see that the large amount of common code in c++ systems makes it hard to pick out the erring 'method'. Any tips would be appreciated. _____________________________________________________________________________ Ken Sayers Dept. Operations Systems Email:ken@aom.ericsson.se Ericsson Telecom AB S-431 84 MOLNDAL SWEDEN Tel: Work: + 46 31 672396 Home: + 46 31 276808 Fax: + 46 31 673777 My opinions are my own, they don't have to agree with my bosses, but it helps sometimes if they do. Tom Stoppard: "We are tied down to a language which makes up in obscurity what it lacks in style "