This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
sim/2183: sim does not support syscall, trap IRQ for powerpc?
- From: muhavid at xko dot cz
- To: gdb-gnats at sources dot redhat dot com
- Date: 8 Oct 2006 12:59:33 -0000
- Subject: sim/2183: sim does not support syscall, trap IRQ for powerpc?
- Reply-to: muhavid at xko dot cz
>Number: 2183
>Category: sim
>Synopsis: sim does not support syscall, trap IRQ for powerpc?
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: support
>Submitter-Id: net
>Arrival-Date: Sun Oct 08 13:08:01 UTC 2006
>Closed-Date:
>Last-Modified:
>Originator: darkanry
>Release: GNU gdb 6.3
>Organization:
>Environment:
Suse 10.0
>Description:
Cannot debug system call, trap. Is it at all possible to debug with target sim for my own os? I've tried with an option:
target sim -r 0x404000 -e bug
But I am always getting a following failure(for a trap):
...
(gdb) cont
cpu 1, cia 0x700: double interrupt - MSR[RI] bit clear when attempting to deliver interrupt, cia=0x700, msr=0x1000; srr0=0x21c4(cia), srr1=0x21002(msr); trap-vector=0x700, trap-msr=0x1000
Program terminated with signal ?, Unknown signal.
The program no longer exists.
(gdb)
...
Am I doing something wrong?
Is there any other option/alernative/patch how to solve it?
thank you for any hint
P.S. Is there at all some command to show a current device configuration?
>How-To-Repeat:
int main(void)
{
//asm("sc");
asm("trap");
return 0;
}
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: