This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
remote/1187: 'call' attempts additional remote 's'tep
- From: baccala at freesoft dot org
- To: gdb-gnats at sources dot redhat dot com
- Date: 24 Apr 2003 00:37:35 -0000
- Subject: remote/1187: 'call' attempts additional remote 's'tep
- Reply-to: baccala at freesoft dot org
>Number: 1187
>Category: remote
>Synopsis: 'call' attempts additional remote 's'tep
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Apr 24 00:38:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: baccala at freesoft dot org
>Release: gdb-5.2.1 gdb-5.3
>Organization:
>Environment:
i386 Linux host / powerpc remote stub
>Description:
after building either gdb-5.2.1 or gdb-5.3 for an Intel
host and powerpc target, then connecting to a remote
powerpc Linux kernel via serial stub, 'call' command
fails. After creating a dummy stack frame, calling it,
returning, and getting the breakpoint, debugger attempts
to continue to program from that point (end of dummy)
resulting in various bizarre malfunctions
>How-To-Repeat:
compile gdb 5.2.1 or gdb 5.3 for intel host, powerpc target
connect to remote powerpc stub (linux-2.4.20 has a bug in
powerpc stub handling, requiring attached patch before it
works) then attempt 'call' command (with remote debugging on)
>Fix:
patch infrun.c at line 2563 (gdb-5.2) adding following code:
if (stop_stack_dummy) { stop_stepping(ecs); return; }
code probably should not reach this point during a stack
dummy call, but does
>Release-Note:
>Audit-Trail:
>Unformatted: