|
I have an application that is crashing once in a while. The crashes are separated by days to weeks. But I see some evidence of the crashes in dmesg: nlc: unhandled page fault at pc=0x2aad13d0, lr=0x2aad13a0 (bad address=0x4d8a8834, code 5)
pc : [<2aad13d0>] lr : [<2aad13a0>] Tainted: PF sp : 7ffffaec ip : 0002353c fp : 7ffffb4c r10: 2aadccc4 r9 : 0002361c r8 : 0002361c r7 : 7ffffaec r6 : 00058460 r5 : 000630a0 r4 : 00058460
r3 : 000630a0 r2 : 00023624 r1 : 00023624 r0 : 4d8a882c Flags: nzCv IRQs on FIQs on Mode USER_32 Segment user Control: C000317F Table: 047CC000 DAC: 00000015 Is there some way I can infer where in my code (presumably program nlc) the page fault occurred? If I do an objdump of nlc, the addresses of the code don't seem to go up to 2aadxxxx territory, just to 17d0c.
ts-7250 with stock kernel, I think: $ cat /proc/version Linux version 2.4.26-ts11 (gcc version 3.3.4) #22 Tue Jun 6 12:23:09 MST 2006 $ -- Rich Wilson __._,_.___
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe __,_._,___ |