Weird Bug - Output redirection causes coredump

Weird Bug - Output redirection causes coredump

Post by Karthikeyan Ramasam » Mon, 26 Feb 1996 04:00:00

I have a program that core dumps when I redirect the output to
a file, but works fine I do not do redirection. Has anybody experienced
this kind of problem? The platform is SUNOS 4.1.3. I do not have any
problems with disk quota or disk getting full or permissions.

Details follow

The program is 'pdfe' that uses tcl and tk interpreter. It in
turn connects to a database server and get the data.  It gives a simple
command line interface for entering data base queries. These database
queries can be redirected from a file. I ran pdfe in two ways

1) Queries from an input file and the output goes into another file

For example

        pdfe < input_file > output_file

If we do this, for some specific input file 'pdfe' core dumps

2) Queries from an input file and the outpuf goes into the stdout

        pdfe < input_file

For the same set of files that caused 'pdfe' coredump in 1) pdfe does
not coredump at all.



1. Fwd: Re: [BUG][2.5.64bk4] Weird problem with 2 PCs - OUTPUT OF PANIC

This is an ongoing conversation and finally the output of the panic.

----------  Forwarded Message  ----------

Subject: Re: [BUG][2.5.64bk4] Weird problem with 2 PCs - OUTPUT OF PANIC
Date: Friday 14 March 2003 10:07 pm

Unable to handle kernel paging request at virtual address 6b6b6b6f
 printing eip:
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0060:[<c012e940>]    Not tainted
EFLAGS: 00010016
EIP is at run_timer_softirq+0xd0/0x3f0
eax: 6b6b6b6b   ebx: c5195150   ecx: 0000006f   edx: c0418d7c
esi: 6b6b6b6b   edi: 6b6b6b6b   ebp: c04189e0   esp: c117fe64
ds: 007b   es: 007b   ss: 0068
Process init (pid: 1, threadinfo=c117e000 task=c117c000)
Stack: c71ea660 c117fee8 c01302a8 c7efc4a0 00000096 00000011 00000011
 c117e000 c117e000 00000001 c04c5c48 fffffffd 00000046 c012965a c04c5c48
 c117e000 c117e000 00000000 c0417520 c010cd05 00000000 c117fee8 c0417520
 c7ffa8f0 Call Trace:
 [<c01302a8>] __dequeue_signal+0x108/0x180
 [<c012965a>] do_softirq+0x9a/0xa0
 [<c010cd05>] do_IRQ+0x235/0x370
 [<c010abf8>] common_interrupt+0x18/0x20
 [<c0125698>] release_task+0x108/0x1a0
[<c0127e72>] wait_task_zombie+0x142/0x1a0
 [<c01282d9>] sys_wait4+0x249/0x290
 [<c011dfa0>] default_wake_function+0x0/0x20
 [<c011dfa0>] default_wake_function+0x0/0x20
 [<c010a28b>] syscall_call+0x7/0xb

Code: 89 50 04 89 02 c7 43 30 00 00 00 00 81 3d e0 89 41 c0 3c 4b
 kernel/timer.c:295: spin_lock(kernel/timer.c:c04189e0) already locked by
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

What's also interesting is when i turned off the A7M266-D before, i got a
spurious 8259A interrupt: IRQ7 spewage, when i turned it back ON the IBM
paniced (as above).

Russel, the patch DID work but you cant use minicom under X to use sysrq (i
could use the command from the IBM console and it did dump the output over
serial so it worked).



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at
Please read the FAQ at

2. System hangs at "Floppy drive(s): fd0 is 1.44M, fd1 is 1.44M"

3. Repost of "Output redirection while reformatting the output"

4. FreeBSD compatibility with Compaq ProLiant

5. Output redirection while reformatting the output

6. Colors...

7. Help: dlopen causes coredump!

8. Problems with netscape

9. umount nfs directory causes coredump

10. fastpatch causes coredump

11. getting SIGSEGV to cause coredump?

12. Running a simple /shell/program causes memory fault (coredump)

13. coredumping / coredumping suid