Well, the process itself will be multi-threaded. That's where the vendor thinks things are going wrong, and the hope is getting the strace output on the processes will allow us to catch an issue as it happens.
Is there a big performance hit in running strace (this is SLES 10) and dumping to a file? It might be easier just to use -o and preventively write all the output beforehand? -- Daniel B. Herrington Director of Field Services Robert Mark Technologies [email protected] o: 651-769-2574 ho: 503-419-6464 m: 503-358-8575 On Thu, 2010-09-02 at 09:56 -0700, Paul Heinlein wrote: > On Thu, 2 Sep 2010, Daniel B. Herrington wrote: > > > All, > > > > Does anyone have good ways to debug running processes without > > restarting them? > > > > I've used truss before, but I've always restarted the process for > > it. Any recommendations would be appreciated. > > You needn't restart a process to use strace/truss. Just point it at an > existing PID: > > strace -p $PID > > It's more difficult, of course, if the parent process starts up > multiple long-lived forks or threads, but a single-threaded process > won't pose any difficulty. > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
