AnsweredAssumed Answered

gdb: SIGTRAP running any program

Question asked by Cary O'Brien on Oct 3, 2014
Latest reply on Nov 6, 2014 by Cary O'Brien

We have a custom P1022 board and are using QorIQ-SDK-V1.6 to create

the software.  u-boot, lernel, and rootfs all run.

 

However, if we try and use gdbserver or even gdb on the board, immediately

upon starting the program (i.e. r) we get

 

warning: [   68.801449] Oops: Exception in kernel mode, sig: 5 [#2]
[   68.807255] SMP NR_CPUS=2 CTI NED
[   68.810564] Modules linked in: cy14b101_nvram(O)
[   68.815183] CPU: 0 PID: 1958 Comm: cp_client Tainted: G      D    O 3.12.19-rt30-QorIQ-SDK-V1.6+gc29fe1a #1
[   68.824915] task: b78c9f80 ti: cfff8000 task.ti: b7858000
[   68.830306] NIP: b000f86c LR: b000f8f4 CTR: b0066bbc
[   68.835262] REGS: cfff9f10 TRAP: 2002   Tainted: G      D    O  (3.12.19-rt30-QorIQ-SDK-V1.6+gc29fe1a)
[   68.844556] MSR: 00021000 <CE,ME>  CR: 22000a22  XER: 00000000
[   68.850396]
GPR00: b000f8f4 b7859f40 b78c9f80 00000000 00000002 00000000 00000000 00000100
GPR08: b7858060 b7858000 00021202 00021000 0020103c 00000000 00000000 10000000
GPR16: 0fff248c 0fff217c fffff000 00000000 0fff0f40 9f8b9668 00000000 0fff20e8
GPR24: 0ffdd678 0fff1d38 0fff2190 0fff0c78 0fff0cd8 0fff1820 0fff1810 9f8b9650
[   68.880134] NIP [b000f86c] recheck+0x10/0x24
[   68.884399] LR [b000f8f4] do_user_signal+0x74/0xc4
[   68.889179] Call Trace:
[   68.891621] [b7859f40] [b000f8f4] do_user_signal+0x74/0xc4 (unreliable)
[   68.898234] --- Exception: 0 at 0xffcfd3c
[   68.898234]     LR = 0xffc3b24
[   68.905274] Instruction dump:
[   68.908235] 3960ffff 7d704ba6 4e800020 7120000c 41820034 614a8000 7d400124 484e12d1
[   68.915993] 3d400002 614a1202 7d400124 54290024 <81290060> 7120000c 40a2ffdc 7120600e
[   68.923929] ---[ end trace 94924a23f071f21e ]---
[   68.928537]
Could not load shared library symbols for linux-vdso32.so.1.
Do you need "set solib-search-path" or "set sysroot"?

 

Program terminated with signal SIGTRAP, Trace/breakpoint trap.
The program no longer exists.

 

Google searching indicates the message about linux-vdso32.so.1 can be ignored.

 

Note that we had to change CONFIG_LOWMEM_SIZE, CONFIG_PAGE_OFFSET, and

CONFIG_KERNEL_START in the defconfig to make space for nor flash.  Could

this be a problem?

 

Ideas?

 

Thanks,

 

Cary O'Brien

Outcomes