----- Original Message ----- > From: "Aaron Davidson" <ilike...@gmail.com> > To: dev@spark.apache.org > Sent: Monday, July 14, 2014 5:21:10 PM > Subject: Re: Profiling Spark tests with YourKit (or something else) > > Out of curiosity, what problems are you seeing with Utils.getCallSite?
Aaron, if I enable call site tracking or CPU profiling in YourKit, many (but not all) Spark test cases will NPE on the line filtering out "getStackTrace" from the stack trace (this is Utils.scala:812 in the current master). I'm not sure if this is a consequence of Thread#getStackTrace including bogus frames when running instrumented or if whatever instrumentation YourKit inserts relies on assumptions that don't always hold for Scala code. best, wb
