[Beowulf] backtraces
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Ashley Pittman apittman at concurrent-thinking.comMon Jun 11 08:36:45 PDT 2007
- Previous message: [Beowulf] backtraces
- Next message: [Beowulf] MPI performance gain with jumbo frames
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 2007-06-11 at 07:32 +0200, Toon Knapen wrote: > Interesting indeed. On which platform is this backtrace.so available > (obtaining backtraces is higly platform dependent AFAIK) ? It's highly dependant to implement but I should imagine most people who need backtraces use a debugger, the libc backtrace() function or libbacktrace which can be use from either inside or outside the target process, these tend to be platform independent. > Mark Hahn wrote: > > I had a user grumble about how it was not trivial to get a basic > > backtrace on our clusters. his jobs tend to be 32-128p, > > and run for a week, so it's not ideal to run them under the debugger. It really shouldn't be that difficult, on a Quadrics cluster at least you can use the command "padb -x -r <rank> <jobid>" from anywhere in the cluster to see a backtrace from any given rank. Ashley,
- Previous message: [Beowulf] backtraces
- Next message: [Beowulf] MPI performance gain with jumbo frames
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
