Re: [linuxtools-dev] Change ValgrindCoreParser to support different valgrind output format

2013-12-05 Thread David Meng
...@eclipse.org [mailto:linuxtools-dev-boun...@eclipse.org] On Behalf Of Aleksandar Kurtakov Sent: Thursday, December 05, 2013 1:05 PM To: Linux Tools developer discussions Subject: Re: [linuxtools-dev] Change ValgrindCoreParser to support different valgrind output format - Original Message

Re: [linuxtools-dev] Change ValgrindCoreParser to support different valgrind output format

2013-12-05 Thread Aleksandar Kurtakov
- Original Message - > From: "Doug Schaefer" > To: "Linux Tools developer discussions" > Sent: Thursday, December 5, 2013 8:45:56 PM > Subject: Re: [linuxtools-dev] Change ValgrindCoreParser to support different > valgrind output format >

Re: [linuxtools-dev] Change ValgrindCoreParser to support different valgrind output format

2013-12-05 Thread Doug Schaefer
08 PM >> Subject: [linuxtools-dev] Change ValgrindCoreParser to support >>different valgrind output format >> >> >> >> Hello, >> >> >> >> We have our own version of valgrind executable running on a remote >>target, >> however the out

Re: [linuxtools-dev] Change ValgrindCoreParser to support different valgrind output format

2013-12-05 Thread Aleksandar Kurtakov
- Original Message - > From: "David Meng" > To: linuxtools-dev@eclipse.org > Sent: Thursday, December 5, 2013 7:32:08 PM > Subject: [linuxtools-dev] Change ValgrindCoreParser to support different > valgrind output format > > > > Hello, > >

[linuxtools-dev] Change ValgrindCoreParser to support different valgrind output format

2013-12-05 Thread David Meng
Hello, We have our own version of valgrind executable running on a remote target, however the output format is a little different from the standard format, which cause trouble parsing the filename and line number using ValgrindCoreParser. There are two possible solutions: 1) Move Valgrind