It appears that gdb can't deal with mips kernel core files. At least I 
could not make it to work.

Regards,
Alex


Andy Ruhl wrote:
> On 12/28/05, Izumi Tsutsui <tsutsui@ceres.dti.ne.jp> wrote:
> 
>>In article <78a2305a0512271847r1201a7fbg18c1f34428498ba7@mail.gmail.com>
>>acruhl@gmail.com wrote:
>>
>>
>>>I'm running 3.0 on my Qube 2, and I got a panic when ftp'ing to the
>>>Qube and getting files.
>>
>>Please post dmesg and exact comand you tried.
>>I can't reproduce the panic on my RaQ2...
> 
> 
> I didn't run a command, I ftp'd to the Qube from another machine
> (NetBSD 3.0 on amd64 to be precise). Here's the line I have in
> inetd.conf:
> 
> ftp             stream  tcp     nowait  root    /usr/libexec/ftpd       ftpd -ll
> 
> Then I did a get of some 300 meg files, but it crashed maybe 5 megs
> after I started the get.
> 
> I think the core didn't dump out completely because gdb says it isn't
> a core file.
> 
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
>     The NetBSD Foundation, Inc.  All rights reserved.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>     The Regents of the University of California.  All rights reserved.
> 
> NetBSD 3.0 (GENERIC) #0: Sun Dec 18 22:39:34 UTC 2005
>         builds@b3.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/cobalt/200512182024Z-obj/home/builds/ab/netbsd-3-0-RELEASE/src/sys/arch/cobalt/compile/GENERIC
> total memory = 160 MB
> avail memory = 153 MB
> mainbus0 (root)
> com0 at mainbus0 addr 0x1c800000 level 3: st16650a, working fifo
> com0: console
> cpu0 at mainbus0: QED RM5200 CPU (0x28a0) Rev. 10.0 with built-in FPU Rev. 10.0
> cpu0: 32KB/32B 2-way set-associative L1 Instruction cache, 48 TLB entries
> cpu0: 32KB/32B 2-way set-associative write-back L1 Data cache
> panel0 at mainbus0 addr 0x1f000000
> gt0 at mainbus0 addr 0x14000000
> pci0 at gt0
> pci0: i/o space, memory space enabled, rd/line, wr/inv ok
> pchb0 at pci0 dev 0 function 0: Galileo GT-64111 System Controller, rev 1
> tlp0 at pci0 dev 7 function 0: DECchip 21143 Ethernet, pass 4.1
> tlp0: interrupting at level 1
> tlp0: Ethernet address 00:10:e0:00:ab:25
> lxtphy0 at tlp0 phy 1: LXT970 10/100 media interface, rev. 3
> lxtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> pcib0 at pci0 dev 9 function 0
> pcib0: VIA Technologies VT82C586 PCI-ISA Bridge, rev 39
> viaide0 at pci0 dev 9 function 1
> viaide0: VIA Technologies VT82C586 (Apollo VP) ATA33 controller
> viaide0: bus-master DMA support present
> viaide0: primary channel configured to compatibility mode
> viaide0: primary channel interrupting at irq 14
> atabus0 at viaide0 channel 0
> viaide0: secondary channel configured to compatibility mode
> viaide0: secondary channel interrupting at irq 15
> atabus1 at viaide0 channel 1
> VIA Technologies VT83C572 USB Controller (USB serial bus, revision
> 0x02) at pci0 dev 9 function 2 not configured
> tlp1 at pci0 dev 12 function 0: DECchip 21143 Ethernet, pass 4.1
> tlp1: interrupting at level 2
> tlp1: Ethernet address 00:10:e0:00:ab:18
> lxtphy1 at tlp1 phy 1: LXT970 10/100 media interface, rev. 3
> lxtphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> Kernelized RAIDframe activated
> wd0 at atabus0 drive 0: <IC35L060AVER07-0>
> wd0: drive supports 16-sector PIO transfers, LBA addressing
> wd0: 58644 MB, 119150 cyl, 16 head, 63 sec, 512 bytes/sect x 120103200 sectors
> wd0: 32-bit data port
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
> wd0(viaide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA)
> boot device: wd0
> root on wd0a dumps on wd0b
> root file system type: ffs
> 
> 
> 
>