How to print stack trace in your java code?

最新推荐文章于 2022-11-15 13:32:03 发布
原创 最新推荐文章于 2022-11-15 13:32:03 发布 · 86 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#Java #thread

本文介绍了两种在Java中打印当前堆栈跟踪的方法：通过创建一个新的Exception实例并调用其printStackTrace()方法；或者使用Thread.currentThread().getStackTrace()来获取表示程序当前堆栈的StackTraceElement数组。

When debugging java code, sometimes it's important to know where you come from. So you can print current stack trace to help you.

 

1. new Exception().printStackTrace();

2. Thread.currentThread().getStackTrace(); This returns an array of StackTraceElement that represents current stack of your program.

“RuntimeError: BlobWriter not loaded“ error when exporting a PyTorch model to CoreML. How to fix it?
suiusoar
07-20 883
将 PyTorch 模型导出到 CoreML 时遇到"RuntimeError: BlobWriter not loaded"这个错误，怎样修复？
Milvus ConnectionRefusedError: how to connect locally
suiusoar
07-02 2026
怎样在本地连接到 Milvus 数据库。连接 Milvus 数据库被拒绝的错误
java printstacktrace_异常处理 - Java中printStackTrace（）方法的用途是什么？
weixin_36064196的博客
02-21 4775
异常处理 - Java中printStackTrace()方法的用途是什么？我正在通过套接字程序。 在其中，在catch块中的IOException对象上调用printStackTrace。printStackTrace()究竟做了什么？catch(IOException ioe){ioe.printStackTrace();}我不知道它的目的。 这有什么用途？9个解决方案91 votes这是S...
得到java异常printStackTrace的详细信息
莫等闲，白了少年头，空悲切
12-17 7929
平时写java代码时，想看抛出的异常信息,来找出具体的异常点，我们常常会用Exception.toString ()或者 Exception.getMessage()来取得异常信息，再把它print到控制台，,但是这些信息只能告诉我们异常本身的信息，对我们找出异常点帮助并不太理想，所以我们会使用Exception.printStackTrace()方法，这样就可以在控制台输出非常详细的异常信息,甚
java异常的栈轨迹记录(stack trace)
liaomingwu的专栏
01-23 3648
java异常的栈轨迹记录(stack trace)，当需要记录异常日志时，可以记录异常的调用堆栈信息，以便根据调用堆栈获取代码位置。
how to print function backtrack with boost
Max_Cong的博客
08-27 1075
How to print current call stack boost::stacktrace::stacktrace contains methods for working with call-stack/backtraces/stacktraces. Here's a small example: #include boost/stacktrace.hpp> // ...
How can I send an email by Java application?
bj_ellen2004的专栏
08-17 1757
原文地址：http://stackoverflow.com/questions/46663/how-can-i-send-an-email-by-java-application-using-gmail-yahoo-or-hotmail#47452 ANSWER 1 First download the JavaMail API and make sure the rele
java print thread id,jstack输出-获取Java Thread.getId的tid
weixin_28973031的博客
03-01 478
I had a look at existing questions on getting the thread id like java-thread-id-and-stack-trace.But I'm not able to figure out something that seemed simple. I want to make a JSP tool to stop a thread ...
how to use dbx in Solaris -Debugging Your Program With dbx
惊鸿一瞥
05-09 6984
发现gdb在Linux上挺好用的，但是在solaris上却不能用，在Solaris上要用dbx。下面就来学习一下如何用dbx. http://docs.oracle.com/cd/E19422-01/819-3683/getting_started.html#pgfId-26812 dbx http://stackoverflow.com/questions/114236/solar
Method in Java--方法
m0_61010858的博客
11-15 534
方法学习记录
An Introduction to Java Stack Traces
Fred Lee的程序人生
04-17 1436
This article shows you step by step how to recognize and collect the clues in a stack trace to solve your Java software problems. What is a Java stack trace? A Java stack trace is a user-friendly sna
How to Gracefully Perform Code Search and Replace in VSCode
# How to Gracefully Perform Code Search and Replace in VSCode ## 1.1 Using the Find Function VSCode offers a powerful find function that allows you to quickly locate text or patterns in your code. ...
请告诉我具体的实验步骤： Lab: system calls In the last lab you used system calls to write a few utilities. In this lab you will add some new system calls to xv6, which will help you understand how they work and will expose you to some of the internals of the xv6 kernel. You will add more system calls in later labs. Before you start coding, read Chapter 2 of the xv6 book, and Sections 4.3 and 4.4 of Chapter 4, and related source files: • The user-space "stubs" that route system calls into the kernel are in user/usys.S, which is generated by user/usys.pl when you run make. Declarations are in user/user.h • The kernel-space code that routes a system call to the kernel function that implements it is in kernel/syscall.c and kernel/syscall.h. • Process-related code is kernel/proc.h and kernel/proc.c. To start the lab, switch to the syscall branch: $ git fetch $ git checkout syscall $ make clean If you run make grade you will see that the grading script cannot exec trace and sysinfotest. Your job is to add the necessary system calls and stubs to make them work. Using gdb (easy) In many cases, print statements will be sufficient to debug your kernel, but sometimes being able to single step through some assembly code or inspecting the variables on the stack is helpful. To learn more about how to run GDB and the common issues that can arise when using GDB, check out this page. To help you become familiar with gdb, run and then fire up gdb in another window (see the gdb bullet on the guidance page). Once you have two windows open, type in the gdb window: make qemu-gdb (gdb) b syscall Breakpoint 1 at 0x80002142: file kernel/syscall.c, line 243. (gdb) c Continuing. [Switching to Thread 1.2] Thread 2 hit Breakpoint 1, syscall () at kernel/syscall.c:243 243 { (gdb) layout src (gdb) backtrace The layout command splits the window in two, showing where gdb is in the source code. The backtrace prints out the stack backtrace. See Using the GNU Debugger for helpful GDB commands. Answer the following questions in answers-syscall.txt. Looking at the backtrace output, which function called syscall? Type a few times to step past struct proc *p = myproc(); Once past this statement, type , which prints the current process's proc struct (see kernel/proc.h>) in hex. np /x *p What is the value of p->trapframe->a7 and what does that value represent? (Hint: look user/initcode.S, the first user program xv6 starts.) The processor is running in kernel mode, and we can print privileged registers such as sstatus (see RISC-V privileged instructions for a description): (gdb) p /x $sstatus What was the previous mode that the CPU was in? In the subsequent part of this lab (or in following labs), it may happen that you make a programming error that causes the xv6 kernel to panic. For example, replace the statement num = p->trapframe->a7; with num = * (int *) 0; at the beginning of syscall, run , and you will see something similar to: make qemu xv6 kernel is booting hart 2 starting hart 1 starting scause 0x000000000000000d sepc=0x000000008000215a stval=0x0000000000000000 panic: kerneltrap Quit out of qemu. To track down the source of a kernel page-fault panic, search for the sepc value printed for the panic you just saw in the file kernel/kernel.asm, which contains the assembly for the compiled kernel. Write down the assembly instruction the kernel is panicing at. Which register corresponds to the variable num? To inspect the state of the processor and the kernel at the faulting instruction, fire up gdb, and set a breakpoint at the faulting epc, like this: (gdb) b *0x000000008000215a Breakpoint 1 at 0x8000215a: file kernel/syscall.c, line 247. (gdb) layout asm (gdb) c Continuing. [Switching to Thread 1.3] Thread 3 hit Breakpoint 1, syscall () at kernel/syscall.c:247 Confirm that the faulting assembly instruction is the same as the one you found above. Why does the kernel crash? Hint: look at figure 3-3 in the text; is address 0 mapped in the kernel address space? Is that confirmed by the value in scause above? (See description of scause in RISC-V privileged instructions) Note that scause was printed by the kernel panic above, but often you need to look at additional info to track down the problem that caused the panic. For example, to find out which user process was running when the kernel paniced, you can print out the process's name: (gdb) p p->name What is the name of the binary that was running when the kernel paniced? What is its process id (pid)? This concludes a brief introduction to tracking down bugs with gdb; it is worth your time to revisit Using the GNU Debugger when tracking down kernel bugs. The guidance page also has some other other useful debugging tips.
最新发布
11-16
- 内核态访问用户指针需用`copyin/copyout`： ```c copyout(p->pagetable, addr, buf, size); ``` 4. **死锁检测** - 在`kernel/spinlock.c`中启用调试： ```c #define DEBUG 1 ``` > 调试提示：启动时...
为什么wait()必须要在放synchronized里面？
渴死的火烈鸟
10-19 2601
假如你要调用某个对象的wait()方法，一般都要放在synchronized声明里面，why? 下面是答案。   Suppose d is the object we're using to invoke wait. When a thread invokes d.wait, it must own the intrinsic lock for d — otherwise an error...
算法：去除字符串中的重复字母
渴死的火烈鸟
11-06 1022
问题：去除字符串中的重复字符，不能使用额外空间（1或者2个变量除外）。 很简单的练手题,但是发现很难写正确。 [code="java"] public class DuplicateChar { //return length of the final string public static int removeDuplicateChar(char []str){ ...
Reading for ParNew (promotion failed) and (concurrent mode failure)
渴死的火烈鸟
09-19 446
http://java-monitor.com/forum/showthread.php?t=645 Dear All, If you are struggling to understand the messages ParNew (promotion failed) and (concurrent mode failure), you might want to bone up o...
ClassFormatError
渴死的火烈鸟
11-02 361
Exception in thread "main" java.lang.ClassFormatError: poi.HelloWorldApp (unrecognized class file version)at java.lang.VMClassLoader.defineClass(libgcj.so.7rh)at java.lang.ClassLoader.defineClass(libg...
Date/Time处理函数总结 [To Do]
渴死的火烈鸟
04-12 343
几种我所用到的用来处理日期，时间的函数总结。 [u][b]Perl[/b][/u] 1. localtime [code="perl"] # 0 1 2 3 4 5 6 7 8 ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); [/code] I...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值