Closed mdoron closed 7 years ago
I think we did something similar, we'll look into that later today.
@mdoron check the StackTrace class, it has this functionality
@rodedzats I only saw it extracts stack trace if it exists, but not specific details within it - I'm talking about ExtractTrace.java.
@mdoron check this class: https://github.com/TechnionYP5777/Bugquery/blob/master/BugQueryServerSide/src/main/java/com/bugquery/serverside/entities/StackTrace.java It extracts the stack trace and saves the exception type and the stack of calls
Tremendous! I will add some functionality right ahead. Is this code going to be on the server side separately from the code of the plugin? If so, I will copy this file to the plugin package - @rodedzats
@mdoron I think you can just import it
I've managed to extract the line number of the first file and put there a comment, I'm working on actually getting the file paths in the stack trace and then it will be pretty much all done. #72
I put this on-hold until I finish #72 since it's a sub-task.
As you're done with #72, I'm removing the on-hold label
Closing this since it's not clear, will open a new one when needed
From stack trace extract lines, files, exception, etc. We need this specifically in order to mark the right position (the line(s)) which yields the exception, but I'm sure we'll find what to do with entire class of parsing.
If the guys who worked on the similarity function did something like this, please inform @rodedzats @yonzarecki.
FYI: @yosefraisman
Clarification: We need a way to get the line numbers of the stack trace.