在QNX中調試核心轉儲 - 如何獲取更多信息？

Question

我以前的工作代碼現在崩潰了。核心轉儲指向被調用的構造函數。 我試圖得到bt，bt完整和反彙編。我需要一些幫助來確定在調用構造函數時可能導致分段錯誤的原因？ 代碼在QNX上運行，並且只有控制檯gdb。局部變量都是0，這意味着什麼？

這裏的O/P：拆卸的

(gdb) bt 
#0 0x481a95b0 in notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID (path_Type=PATH_NULL, pathId=1215822164, 
    alarm_Id=DS3_PATH_IDLE_ID) at /vob/qnx/cema-common/msg/PathObjMsg.h:47 
(gdb) bt full 
#0 0x481a95b0 in notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID (path_Type=PATH_NULL, pathId=1215822164, 
    alarm_Id=DS3_PATH_IDLE_ID) at /vob/qnx/cema-common/msg/PathObjMsg.h:47 
     msg = {<Message> = {msgSource = MSG_SOURCE_INVALID, msgPriority = MSG_PRIO_LOW, msgLength = 0}, 
    msgType = MSG_PATH_ALARM, pathType = PATH_NULL, pathId = {bay = 0 '\0', line = 0 '\0', path = {stsn = { 
     sts1Num = 0 '\0'}, vt = {sts1Num = 0 '\0', isTu3 = 0 '\0', tug3Num = 0 '\0', vtgTug2Num = 0 '\0', 
     vtTuNum = 0 '\0'}, ds3 = {sts1Num = 0 '\0', ds3Num = 0 '\0'}, ds1InDS3Line = {pad = 0 '\0', ds1Num = 0 '\0'}, 
     ds1InVT = {sts1Num = 0 '\0', pad = 0 '\0', tug3Num = 0 '\0', vtgTug2Num = 0 '\0', vtTuNum = 0 '\0'}, 
     ds1InDS3Path = {sts1Num = 0 '\0', tug3Num = 0 '\0', ds1Num = 0 '\0'}, e1InVT = {sts1Num = 0 '\0', pad = 0 '\0', 
     tug3Num = 0 '\0', vtgTug2Num = 0 '\0', vtTuNum = 0 '\0'}, e3 = {sts1Num = 0 '\0', ds3Num = 0 '\0'}}}, 
    alarmId = 0, lineId = 0 '\0'} 
     emPathType = PATH_NULL 
     emAlarmId = 10 

(gdb) l * 0x481a95b0 
0x481a95b0 is in notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID (/vob/qnx/cema-common/msg/PathObjMsg.h:47). 

42   PathObjMsg(
43    PATH_TYPE pathTypeIn, 
44    EM_PATH_ID pathIdIn, 
45    PATH_OBJ_MSG_TYPE msgTypeIn, 
46    EM_PATH_ALARM_ID alarmIdIn 
**47   ): Message(MSG_SOURCE_PATH_OBJ)** 
48   { 
49    pathType = pathTypeIn; 
50    pathId = pathIdIn; 
51    msgType = msgTypeIn; 

O/P：現在

bne-  0x481a962c <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+264> 
0x481a959c <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+120>: li  r0,15 
0x481a95a0 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+124>: mr  r27,r28 
0x481a95a4 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+128>: stw  r27,88(r1) 
0x481a95a8 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+132>: stw  r0,8(r1) 
0x481a95ac <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+136>: addi r31,r1,8 
0x481a95b0 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+140>: li  r9,1 
0x481a95b4 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+144>: stw  r9,4(r31) 
0x481a95b8 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+148>: stw  r29,16(r31) 
0x481a95bc <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+152>: lwz  r0,88(r1) 
0x481a95c0 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+156>: stw  r9,12(r31) 
0x481a95c4 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+160>: stw  r0,20(r31) 
0x481a95c8 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+164>: stw  r5,24(r31) 
0x481a95cc <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+168>: lbz  r0,89(r1) 
0x481a95d0 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+172>: mr  r3,r31 
0x481a95d4 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+176>: stb  r0,28(r31) 
0x481a95d8 <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+180>: li  r4,32 
0x481a95dc <notifyDs3PathAlarmClrEvent__F9PATH_TYPEUi17DS3_PATH_ALARM_ID+184>: 

Answer 1

我以前的工作代碼崩潰。核心轉儲指向正在調用的構造函數 。我已經試圖獲得bt，bt full和 反彙編。我需要一些幫助來確定在調用構造函數時可能導致段錯誤的原因是什麼？代碼在QNX上運行，並且 只有控制檯gdb。局部變量全部爲0，那麼 這意味着什麼？我需要一些幫助來確定在調用構造函數時可能導致段錯誤的原因是什麼？

請不要斷定調用構造函數時可能有問題（僅）。這可能僅僅是已經發生的其他（不良）副作用。 很難從當前堆棧跟蹤中找出問題。某些時候，內存錯誤會非常間歇地（由於不同的輸入/線程/執行順序的變化）在非常間歇的（程序可能會運行多年，而不會出現任何問題的症狀）。 當地人變量0可能表明它看起來不錯，但我們不能從中得出任何結論。

我確實覺得可能會有一些內存損壞情況（您其他模塊中的其他某個地方）正在領導此次崩潰。您將不得不使用GDB/Valgrind（某些動態工具）來調試代碼，以找出根本問題。看起來您在QNX上遇到了這個問題，因此您可能需要運行Valgrind來識別代碼中的問題。你可以參考我以前的帖子

https://stackoverflow.com/a/22658693/2724703