trace命令是否支持内部方法的所有链路查看?
- Dominant language
- Java
- Stars
- 37.6k
- Forks
- 7.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
- [ ] 我已经在 [issues](https://github.com/alibaba/arthas/issues) 里搜索,没有重复的issue。
### 环境信息
* `arthas-boot.jar` 或者 `as.sh` 的版本: xxx
* Arthas 版本: xxx
* 操作系统版本: xxx
* 目标进程的JVM版本: xxx
* 执行`arthas-boot`的版本: xxx
### 重现问题的步骤
目前只显示方法内部方法的调用,如果内部方法还有很多调用则显示不全,比如我有一个导入功能,他只能显示
psdi.webclient.beans.intobject.ImportBean()
psdi.webclient.beans.intobject.ImportBean#loadImport(UploadFile file)
### 我的期望的结果是(内部调用的方法也需要全部显示,一般用于源码分析):
psdi.webclient.beans.intobject.ImportBean()
psdi.webclient.beans.intobject.ImportBean#loadImport(UploadFile file)
psdi.iface.app.common.MaxIfaceLoad#importData(InputStream in)
com.ibm.tivoli.maximo.load.OSFlatFileLoaderImpl#processObjectStructureFlatData(InputStream inStream, String osName, String messageType, MboRemote npMbo)
com.ibm.tivoli.maximo.load.BaseFlatFileParser#nextRecord() 返回List>
BaseFlatToXMLConverter xmlConverter = new BaseFlatToXMLConverter(lst, osName, parser.getAction(), parser.getTransLanguage(), messageType);
psdi.iface.intertables.BaseFlatToXMLConverter#convert()
psdi.iface.intertables.BaseFlatToXMLConverter#prepareObjectXML(MosDetailInfo mic, int parentCount)
psdi.iface.intertables.BaseFlatToXMLConverter#createObjectAttrElement(IfaceColumnInfo colInfo)
com.ibm.xml.xlxp.api.stax.XMLOutputFactoryImpl.XMLStreamWriterProxy#writeCharacters(String var1)
com.ibm.xml.xlxp.api.stax.XMLStreamWriterImpl#writeCharacters(String var1)
com.ibm.xml.xlxp.api.stax.XMLStreamWriterImpl#escapeAndWrite(String var1, byte[] var2)
com.ibm.xml.xlxp.api.stax.XMLStreamWriterImpl#escapeAndWrite(char[] var1, int var2, int var3, byte[] var4)
com.ibm.xml.xlxp.api.stax.serializer.UTF8Writer#write(char[] var1, int var2, int var3)
### 实际运行的结果
实际运行结果,最好有详细的日志,异常栈。尽量贴文本。
```
把异常信息贴到这里
```
Contributor guide
Research direction
Start with the Arthas `trace` command and reproduce the reported import call chain using the example in the issue. Determine whether nested internal calls are intentionally limited, then define the complete-chain behavior and verify it against the expected call hierarchy shown in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100