------Original Message------
From: [EMAIL PROTECTED]
To: Michael Slater <[EMAIL PROTECTED]>
Sent: March 7, 2000 9:52:50 AM GMT
Subject: Re: dynamically linked binaries causing panic
>we are able to run simple executables ( e.g with s printf ) which are
>statically linked but the ones which are dynamically linked are causing
>kernel panic.
What does the panic look like?
p.
hi phil,
here is what the panic looks like ( test2 is a dynamically linked
executable with a single printf for the body )
IF NECESSARY# test2
Kernel panic: Unknown data abort code 0 [pc=4002f798, *pc=005f5f72]
LR=4002f798
received signal SIGINT, Interrupt.
panic (fmt=0xc076ffb4 "\230�\002@\234�\002@$") at panic.c:78
78 for(;;) {
--------------------------------------------------------------
(gdb)r
program om being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /root/patches/bootsim/../linux/vmlinux
Internal error: branch through zero: 0
CPU: 0
pc : [<00000004>] lr : [<4002f79c>]
sp : bffff9cc ip : c076ff94 fp : c076ffa0
r10: 4001d404 r9 : bffff9f0 r8 : bffff9f0
r7 : 400164f8 r6 : 40101ea0 r5 : 24242424 r4 : c00b8dcc
r3 : 60000013 r2 : 00000007 r1 : 00000000 r0 : 00000000
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment user
INTSR1 0x00001000 INTMR1 0x00002200
INTSR2 0x00000000 INTMR2 0x00000000
INTSR3 0x00000000 INTMR3 0x00000000
Control: 017D Table: C07C8000 DAC: 00000015
Process test2 (pid: 10, stackpage=c076f000)
Stack:
c076ff80: 4002f79c 00000004 60000013 00000000 00000000 c076ffb4
c0041d08
c076ffa0: c00477f0 c0041c5c 00000000 4002f798 005f5f72 4002f798 4002f79c
00000024
c076ffc0: 40027d14 4002f79c 7efefeff 24242424 40101ea0 400164f8 bffff9f0
bffff9f0
c076ffe0: 4001d404 bffff9e0 bffff9e4 bffff9cc 4002f79c 4002f798 60000010
ffffffff
Backtrace:
Function entered at [<c00477e0>] from [<c0041d08>]
Code: pc not in code space
FORK IF NECESSARYFORKING FORKING SHELL IN PARENT PARENT PROCESSFORK ARGS=0#
ls
hello world
busyboxcatchgrpchmodchowncpdatedddfdmesgdudutmpfalsegrepgunzipgzipheadhostnamekillln
lslsmodmkdirmknodmoremount
----------------------------------------------------------------
as u can see, the kernel panics and enters an infinite loop. after i came to
the gdb prompt, i ran it again to get the second part of the dump i have
sent.
i should mention here that the initrd i am using uses the BusyBox utility (
www.lineo.org ) which was statically linked.
we had our own initrd with the shell and commands dynamically linked. none
except the built in commands ( echo ) worked.we add the dump for this too -
# ls
sh: memory violation at pc=0x02005158, lr=0x020050e0 (bad
address=0x020009c4, code 1)
# echo ghg
ghg
# ls
Unable to handle kernel paging request at virtual address 80037134
current->tss.memmap = C0770000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 2
CPU: 0
pc : [<c003a384>] lr : [<80037138>]
sp : c0281fb8 ip : 400fed5c fp : 00000000
r10: 80048770 r9 : 00000000 r8 : c0282000
r7 : 020166f8 r6 : 60000010 r5 : 00000001 r4 : bffffd58
r3 : 00000710 r2 : fffee9c4 r1 : 801fe578 r0 : 400164f8
Flags: nZCv IRQs off FIQs on Mode SVC_32 Segment user
Control: 017D Table: C0770000 DAC: 00000015
Process sh (pid: 8, stackpage=c0281000)
Stack:
c0281fa0: 80037138 c003a384 60000093 ffffffff 400164f8
801fe578
c0281fc0: fffee9c4 00000710 bffffd58 00000001 020009ac 020166f8 0200b9f4
00000000
c0281fe0: 80048770 40034044 400fed5c 40034044 4000c0a4 80037138 60000010
400164f8
Code: e4880004 e3a0b000 (e51e6004) e206740f e337040f
# cd bin
# pwd
/bin
any pointers towards why this is happening?
apologies for the longish mail
slater
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com?sr=mc.mk.mcm.tag001
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
