gdb optimized out错误解决

最新推荐文章于 2020-06-12 00:02:13 发布
转载 最新推荐文章于 2020-06-12 00:02:13 发布 · 1.8w 阅读 · 1

本文介绍了在使用Linux GDB进行调试时遇到变量值被优化掉的问题及解决方案。当使用如-O2等优化选项编译时，可能会导致GDB无法正确显示变量值。解决办法是关闭编译优化选项，改为使用-O0，这样可以避免源代码行误导问题。

when linux gdb debug, print a variable, such as i,  by command p i;

 

The gdb output  value optimized out.

 

The solution for the problem is off the compile optimation option -Ox,  x note digital, such 2, 3, 4 etc


The better way is that changing -Ox to -O0.

The -O0 denotes there is no optimization. It will avoid gdb mislead source code line issue.

gdb 进阶使用记录（主要是关于 optimized out）
qq_38781075的博客
04-26 2902
如果 gdb 调试发现 optimized out，这个表示被编译器优化了，这个优化跟编译选项有关，gcc 有个 -O0 -O1 -O2 等编译选项，越高等级能看到的信息越少。
gdb value optimized out
fanbird2008的专栏
05-06 1万+
when linux gdb debug, print a variable, such as i,  by command p i;   The gdb output  value optimized out.   The solution for the problem is off the compile optimation option -Ox,  x note digital,
gdb 出现value optimized out
fengfeifengfei的专栏
03-06 1629
gdb调试程序的时候打印变量值会出现 情况,可以在gcc编译的时候加上 -O0参数项,意思是不进行编译优化,调试的时候就会顺畅了,运行流程不会跳来跳去的,发布项目的时候记得不要在使用 -O0参数项,gcc 默认编译或加上-O2优化编译会提高程序运行速度.
<转载>linux gcc编译器中使用gdb单步调试程序，程序不是顺序执行的。
weixin_34346099的博客
08-26 705
原文地址http://blog.youkuaiyun.com/abc78400123/article/details/6779108   　　在用gdb调试，使用s 或n单步执行程序时，发现程序不是按顺序运行的，有时莫名其妙的执行到前面的语句去了，有时又执行到后面的语句，有时一次执行几条语句。后来查了下资料。原来这是编译时的优化问题所导致的。 因为内核的编译是使用make命令的，所以要更改优化等级的话，...
gdb调试 出现value optimized out解决方法
任我行的博客
06-12 1万+
现象： gdb调试 出现value optimized out解决方法 原因： 由于gcc在编译过程中默认使用-O2优化选项，希望进行单步跟踪调试时，应使用-O0选项。 解决办法： 使用-O0选项 附录（优化等级的说明）： 这个选项控制所有的优化等级。使用优化选项会使编译过程耗费更多的时间，并且占用更多的内存，尤其是在提高优化等级的时候。 -O设置一共有五种：-O0、-O1、-O2、-O3和-Os。除了-O0以外，每一个-O设置都会多启用几个选项，请查阅gcc手册的优化选项章节： -O0：这个等级（字母“
GDB调试时，出现value optimized out的解决办法小结
JosiasAnas的博客
05-29 2291
原因在于在对代码进行编译的时候默认开启了-O2选项，解决方法； 1.单个C/C++文件进行编译时，可直接将-o更改为-O0，即编译时不进行优化； 2.工程文件MakeFile中，可添加如下标签： C optimization flags COPT =-O0 -funroll-loops 3.利用Cmake进行编译时，在cmakelist中修改如下: Add -O0 to remove optimizations when using gcc IF(CMAKE_COMPILER_IS_GNUCC) set(C
#0 tpsocket_event_filelog_to_hub (handler=<optimized out>, buf=0xbe8b5c08, event=10) at storage.c:906 sock = <optimized out> session = 0x0 decrypt_flag = <optimized out> nbuf = <optimized out> __FUNCTION__ = "tpsocket_event_filelog_to_hub" final_file = <optimized out> #1 0xb6b8da2c in tpsocket_event (sock=sock@entry=0xd370e0, event=event@entry=10) at tpsocket_fd.c:107 dummy = {next = 0xbe8b5c08, prev = 0xbe8b5c08} ret = true empty_write = 1 __func__ = "tpsocket_event" #2 0xb6b8eaf6 in tpsocket_data_cb (ufd=0xd371a4, events=<optimized out>) at tpsocket_fd.c:1487 wret = 0 rret = <optimized out> nice = <optimized out> rlen = 0 wlen = 83 wait = <optimized out> sock = 0xd370e0 __func__ = "tpsocket_data_cb" #3 0xb6bba6f2 in uloop_run_events (timeout=<optimized out>) at /home/wuyilun/Desktop/CAMEOS/platform/build_dir/target-arm-sigmastar-linux-uclibcgnueabihf/libubox-2016-07-29/uloop.c:192 stack_cur = {next = 0x0, fd = 0xd371a4, events = 0} events = <optimized out> cur = <optimized out> fd = 0xd371a4 cur = <optimized out> fd = <optimized out> stack_cur = <optimized out> events = <optimized out> #4 uloop_run () at /home/wuyilun/Desktop/CAMEOS/platform/build_dir/target-arm-sigmastar-linux-uclibcgnueabihf/libubox-2016-07-29/uloop.c:543 recursive_calls = 1 tv = {tv_sec = 1268, tv_usec = 765487} #5 0x0001ab0c in main (argc=<optimized out>, argv=<optimized out>) at main.c:388 __FUNCTION__ = "main" final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> (gdb) #0 tpsocket_event_filelog_to_hub (handler=<optimized out>, buf=0xbe8b5c08, event=10) at storage.c:906 sock = <optimized out> session = 0x0 decrypt_flag = <optimized out> nbuf = <optimized out> __FUNCTION__ = "tpsocket_event_filelog_to_hub" final_file = <optimized out> #1 0xb6b8da2c in tpsocket_event (sock=sock@entry=0xd370e0, event=event@entry=10) at tpsocket_fd.c:107 dummy = {next = 0xbe8b5c08, prev = 0xbe8b5c08} ret = true empty_write = 1 __func__ = "tpsocket_event" #2 0xb6b8eaf6 in tpsocket_data_cb (ufd=0xd371a4, events=<optimized out>) at tpsocket_fd.c:1487 wret = 0 rret = <optimized out> nice = <optimized out> rlen = 0 wlen = 83 wait = <optimized out> sock = 0xd370e0 __func__ = "tpsocket_data_cb" #3 0xb6bba6f2 in uloop_run_events (timeout=<optimized out>) at /home/wuyilun/Desktop/CAMEOS/platform/build_dir/target-arm-sigmastar-linux-uclibcgnueabihf/libubox-2016-07-29/uloop.c:192 stack_cur = {next = 0x0, fd = 0xd371a4, events = 0} events = <optimized out> cur = <optimized out> fd = 0xd371a4 cur = <optimized out> fd = <optimized out> stack_cur = <optimized out> events = <optimized out> #4 uloop_run () at /home/wuyilun/Desktop/CAMEOS/platform/build_dir/target-arm-sigmastar-linux-uclibcgnueabihf/libubox-2016-07-29/uloop.c:543 recursive_calls = 1 tv = {tv_sec = 1268, tv_usec = 765487} #5 0x0001ab0c in main (argc=<optimized out>, argv=<optimized out>) at main.c:388 __FUNCTION__ = "main" final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> (gdb) 帮我改正。
11-03
- `final_file = <optimized out>` 表示该变量被编译器优化，无法查看其值，可能需要关闭编译优化重新编译程序。 ### 改正建议 1. **检查空指针访问**： ```c if (session == NULL) { // 处理错误，例如记录...
#1 0x00048dde in tpsocket_event_filelog_to_hub (handler=0xd380f0, buf=0xd3822c, event=8) at worker.c:4136 request_value = "Ua6jXbNl9rpVijWQKgTfUPhq4dwuSeTKyfjQZ33Nf6mVSO3Tvm/Sk/b3oqoJAIY4HCMTWYGJfAZcDVsOl3XCkEhFcaoedmOtGyLm5jhAkCNreaXmTqAZ+upwyQ3ZWdY8ThKq8oTK9xggLtAnp7hATStvKCySA2HEUT50Qla25Yumy+rVRY2lVucmlmAJxxFpX15FTJea"... final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> sock = 0xd380e0 __FUNCTION__ = "tpsocket_event_filelog_to_hub" session = 0xd55ae8 decrypt_flag = 0 nbuf = <optimized out> fp = 0xd55aa0 remaining = 3150 filepath = <optimized out> input_data = 0xd561f3 "{\"method\":\"securePassthrough\",\"params\":{\"request\":\"Ua6jXbNl9rpVijWQKgTfUPhq4dwuSeTKyfjQZ33Nf6mVSO3Tvm/Sk/b3oqoJAIY4HCMTWYGJfAZcDVsOl3XCkEhFcaoedmOtGyLm5jhAkCNreaXmTqAZ+upwyQ3ZWdY8ThKq8oTK9xggLtAnp7hAT"... input_len = 3150 error = false decoded_data = 0x0 decoded_len = 0 plain_len = 0 plain_data = 0x0 final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> #2 0xb6bee9b4 in tpsocket_event (sock=sock@entry=0xd380e0, event=event@entry=8) at tpsocket_fd.c:112 ret = true empty_write = 1 __func__ = "tpsocket_event" #3 0xb6bf8794 in tpsocket_process_http (buf=0xd56068, sock=0xd380e0) at tpsocket_parser.c:4336 len = <optimized out> body = <optimized out> state = 9 parser = 0xd38240 state = <optimized out> parser = <optimized out> __func__ = "tpsocket_process_http" line = <optimized out> rtp = <optimized out> data = <optimized out> _s = <optimized out> _s = <optimized out> len = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> --Type <RET> for more, q to quit, c to continue without paging--
最新发布
11-07
这在正常情况下不会出错，但如果你传入的 `request_value` 是 `NULL` 或者不是有效的字符串（没有 `\0` 结尾），就会导致 **段错误（Segmentation Fault）**。 --- ### GDB 输出分析 - `request_value` 看起来是...
(gdb) bt full (gdb) bt full #0 SignalKill () at /builds/workspace/Q0S22x-SDP/build_aarch64/lib/c/kercalls/aarch64/SignalKill.S:8 No locals. #1 0x000000007819f440 in abort () at /builds/workspace/Q0S22x-SDP/build_aarch64/lib/c/ansi/abort.c:93 dflact = { in un = { in handler = 0x0, in sigaction = 0x0}, in flags = 0, in mask = { bits = {32, 0}}} action = { in un = { in handler = 0x0, in sigaction = 0x0}, in flags = 0, in mask = { bits = {0, 0}}} #2 0x00000000781b60d4 in malloc mutex lock ( mutex=<optimized out>) at /builds/workspace/Q0S22X-SDP/build_aarch64/lib/c/alloc/malloc ommon.h:54 No locals. #3 mutex spintrylock ( mutex=<optimized out>, stats=<optimized out>, stats=<optimized out>, _max_spin=<optimized out>) at /builds/workspace/Q0S22x-SDP/build aarch64/lib/c/alloc/malloc-common.h:76 retry = <optimized out> status = <optimized out> retry = <optimized out> status = <optimized out> #4 malloc_lock (size=3976, lockl=1) at /builds/workspace/Q0S22x-SDP/build_aarch64/lib/c/alloc/malloc.c:469 v = <optimized out> p = <optimized out> x = <optimized out> i = <optimized out> ret = <optimized out> idx = <optimized out> #5 0x000000007800fe64 in ?? () No symbol table info available. #6 0x0000000010122000 in vBsdAd ISH PollList No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) (adh)
08-16
我们正在处理一个关于使用GDB调试程序崩溃的问题。用户特别提到了backtrace分析，以及崩溃可能与malloc、mutex lock和abort调用相关。 根据引用内容，我们可以总结以下关键点： 1. 使用gdb加载core文件：`gdb -c ./...
#0 0xb661b9ca in __malloc_consolidate () from /home/wuyilun/Desktop/CAMEOS/platform/staging_dir/target-arm-sigmastar-linux-uclibcgnueabihf/root-model_sstar_ssr920/lib/libc.so.0 No symbol table info available. #1 0xb661be96 in malloc () from /home/wuyilun/Desktop/CAMEOS/platform/staging_dir/target-arm-sigmastar-linux-uclibcgnueabihf/root-model_sstar_ssr920/lib/libc.so.0 No symbol table info available. #2 0xb661c53c in calloc () from /home/wuyilun/Desktop/CAMEOS/platform/staging_dir/target-arm-sigmastar-linux-uclibcgnueabihf/root-model_sstar_ssr920/lib/libc.so.0 No symbol table info available. #3 0x00044376 in tpsocket_event_filelog_to_hub (handler=0xd370a0, buf=0xd371dc, event=8) at storage.c:952 decoded_len = <optimized out> plain_data = <optimized out> plain_len = 1 final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> input_data = 0xd551c3 "RuLShVIdnAlmFnlmaUbHxR03a146YhY6zndf5ssXuNkY3wnk15bVlUEDQ0e8sHo0/WnrIgHrk8jH/+L7fHv4jxrXR7Fd8YPJbGIbD+DmweEuilgiYmZ0cvo843nHeWxk+zIzKxV55QBD9FUVZzawC1dRRxZGJTpyNKczhVG8IZCfn3XXqLt3hJ+X73Ylo06IsYSiEtbd"... decoded_data = 0x0 error = false input_len = 2476 final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> final_file = <optimized out> sock = 0xd37090 session = 0xd37830 decrypt_flag = 1 nbuf = 0xd54df8 fp = 0xd54e48 remaining = 2476 filepath = 0xd37834 "/mnt/sd_card/40AE30181089/log.txt" __FUNCTION__ = "tpsocket_event_filelog_to_hub" final_file = <optimized out> #4 0xb6c429b4 in tpsocket_event (sock=sock@entry=0xd37090, event=event@entry=8) at tpsocket_fd.c:112 ret = true empty_write = 1 __func__ = "tpsocket_event" #5 0xb6c4c5c0 in tpsocket_process_http (buf=0xd55028, sock=0xd37090) at tpsocket_parser.c:4336 len = <optimized out> body = <optimized out> state = 24 parser = 0xd371f0 state = <optimized out> parser = <optimized out> __func__ = "tpsocket_process_http" line = <optimized out> rtp = <optimized out> data = <optimized out> _s = <optimized out> _s = <optimized out> len = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> _s = <optimized out> --Type <RET> for more, q to quit, c to continue without paging--
11-03
从你提供的 **GDB 崩溃栈信息**来看，程序崩溃在 `calloc` 调用期间，具体是： ``` #3 0x00044376 in tpsocket_event_filelog_to_hub (handler=0xd370a0, buf=0xd371dc, event=8) at storage.c:952 ``` 并且在执行...
value has been optimized out
llrraa2010的专栏
04-20 6462
use the typecasted address to print: p *((Object*)0xb6ffe050)->clazz findClassFromLoaderNoInit (descriptor=0x80925e8 "LFoo;", loader=0xb6ffe050)     at dalvik/vm/oo/Class.c:1243 1243    dotNa
GDB变量值显示为 optimized_out 的解决方法
私房菜
12-23 2万+
最近使用GDB调试的时候，经常遇到GDB查看变量值的时候输出< optimized_out >，Google了一下，找到几个解决方法，来应对不通情况下需要查看具体变量输出的场景。 解决方案 将GCC优化选项调整为O1或是O0 GCC在O2、O3优化选项下会将代码优化的比较多，调试器有可能会找不到变量的信息。通常可以将优化级别降低到O0，完全关闭优化，可以保留所有的变量和代码...
value optimized out
hxb3530的专栏
05-07 660
去掉-O之类的优化参数
cocos2dx在xcode下调试看不到变量数据－value may have been optimized out
Ts1030746080的专栏
12-29 3193
如果在程序输出信息时，看到value may have been optimized out。那说明，启用了编译器优化选项，无法显示该变量的值。 解决办法：关掉编译器优化（如:-O2，删除即可）。
CMAKList添加防止 value has been optimized out
qq_31638535的博客
01-28 934
# Add -O0 to remove optimizations when using gcc IF(CMAKE_COMPILER_IS_GNUCC) set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -O0") set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -O0") EN...
内核调试出现value optimized out的问题
jasonLee的博客
08-27 5951
最近在用gdb调试内核的过程中经常会有&lt; value optimized out&gt;的提示， 首先分析该提示出现的原因，我的理解是可能这些被优化的变量已从内存中被移到了寄存器中，所以会找不到。 为了能在调试过程中看到所有的变量，不知道能不把内核编译为-O0？若可以的话，又需要在什么地方来改呢？ 在所有的CONFIG中，我只发现了一个CONFIG_CC_OPTIMIZE_FOR_SI...
关于gdb value optimized out的解决方式
热门推荐
Andy.Wang的博客
01-20 3万+
关于gdb value optimized out的解决方式
Eclipse调试出现value optimized out的解决方法
Ethan.W
04-16 5597
今天在ubuntu上用eclipse调试程序时，发现有许多变量值显示为 value optimized out其实这是因为编译的时候开启了优化选项 -On (n=1,2,3)，经过优化后gdb有时候不能正确的显示源代码的某些变量。解决的方法很简单，在调试的时候将编译选项-On 更改为 -O0停止优化，正式出版本的时候再开启优化以提升性能
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值