| Summary: | The ParseHeapDump script doesn't run on AIX | ||
|---|---|---|---|
| Product: | [Tools] MAT | Reporter: | Andrew Johnson <andrew_johnson> |
| Component: | Core | Assignee: | Project Inbox <mat.core-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | ||
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | AIX Motif | ||
| Whiteboard: | |||
|
Description
Andrew Johnson
I've removed the CR/LF by changing the svn:mime-type to text/plain, then locally renaming the file to ParseHeapDump.sh.txt, then file->convert line delimiters->Unix, then renamed the file back to ParseHeapDump.sh I've created a ParseHeapDump2.sh script for AIX which will run with 32-bit and 64-bit Java. Does it make sense to have both files included in the RCP? I think it will be better to give to the user only one script which is working on the platform. Or did I interpret wrongly the build.properties file? The existing ParseHeapDump.sh script runs on AIX with 32-bit Java. Is it better to use this script which will also use MemoryAnalyzer.ini for heap size, and other parameters the same as the GUI version etc. http://wiki.eclipse.org/index.php/MemoryAnalyzer/FAQ#Out_of_Memory_Error_while_Running_the_Memory_Analyzer or to always use the new ParseHeapDump2.sh script (renamed to ParseHeapDump.sh) on AIX? I would say either rename ParseHeapDump2.sh to ParseHeapDump.sh and use only it, or rename ParseHeapDump2.sh to ParseHeapDump64.sh and keep both. I just didn't like the 2 at the end, as it tells nothing about when to use this script. I've just put one script for AIX which should run with 32-bit and 64-bit Java. |