public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: carsten_schlote@gmx.net
To: insight-gnats@sources.redhat.com
Subject: insight/212: broken mipsisa64-*-* build, broken $pc / breakpoint handling.
Date: Tue, 04 Mar 2003 15:23:00 -0000	[thread overview]
Message-ID: <20030304151621.16655.qmail@sources.redhat.com> (raw)


>Number:         212
>Category:       insight
>Synopsis:       broken mipsisa64-*-* build, broken $pc / breakpoint handling.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 04 15:23:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Carsten Schlote
>Release:        insight-5.3-release
>Organization:
>Environment:
suse linux 8.1
>Description:
The simulator works fine, but gdb seems to unable to handle breakpoints / stop the simulator. It will stop with:

(gdb) b Suite_SuiteGetCmdLine
Breakpoint 1 at 0x8001cb7c: file suite_misc.c, line 55.
(gdb) run
Starting program: /home/csc/src/aos64cvs/aos64core/build/mips-gdbsim/images/image.elf

Program received signal SIGTRAP, Trace/breakpoint trap.
warning: Warning: GDB can't find the start of the function at 0xffffffff.
0xffffffffffffffff in ?? ()
>How-To-Repeat:
Compile gdb/insight for mipsisa64 target. Compile some mips64 program. Set a breakpoint somewhere. run it. 
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-03-04 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 15:23 carsten_schlote [this message]
2003-03-04 17:33 cgd
2003-03-28 19:30 kseitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030304151621.16655.qmail@sources.redhat.com \
    --to=carsten_schlote@gmx.net \
    --cc=insight-gnats@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).