On Friday, August 20, 2010, Andreas Zwinkau wrote: > Tangential questions: > What is it about those SIGPWR and SIGXCPU signals? Is this internal x10 > behavior? What for?
Dear Andreas, sorry for the late answer. I am just debugging my X10 program using ddd (which uses gdb underneath). I was also stumbling over SIGPWR signals. I found the answer to the above question elsewhere in this forum. On Thursday, June 10, 2010, Igor Peshansky wrote: > Sorry, should've mentioned it. SIGPWR and SIGXCPU are used by the garbage > collector, and should be ignored. We have a recommended gdb script that > sets up gdb appropriately: > > # a few things that are useful for debugging x10 programs with gdb > set print static-members off > break x10aux::throwNPE > break x10aux::throwBPE > break x10aux::throwArrayIndexOutOfBoundsException > break x10aux::throwOOME > handle SIGPWR SIGXCPU nostop noprint > > Hope this helps, > Igor -- Mit freundlichen Grüßen / Kind regards Dr. Christoph Pospiech High Performance & Parallel Computing Phone: +49-351 86269826 Mobile: +49-171-765 5871 E-Mail: christoph.pospi...@de.ibm.com ------------------------------------- IBM Deutschland GmbH Vorsitzender des Aufsichtsrats: Erich Clementi Geschäftsführung: Martin Jetter (Vorsitzender), Reinhard Reschke, Christoph Grandpierre, Klaus Lintelmann, Michael Diemer, Martina Koederitz Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 14562 WEEE-Reg.-Nr. DE 99369940 ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ X10-users mailing list X10-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/x10-users
