From: James Ingham <jingham@cygnus.com>
To: "Serge Nikulin" <nikulin@actsw.amat.com>
Cc: <insight@sourceware.cygnus.com>
Subject: Re: Bug in M68K-targeted insight (crash)
Date: Mon, 24 Apr 2000 11:06:00 -0000 [thread overview]
Message-ID: <14596.36284.258460.711769@leda.cygnus.com> (raw)
In-Reply-To: <004d01bfabd8$cb640a80$35758798@mis.amat.com>
Serge,
This is a core gdb bug, not an insight specific bug. You should make
a patch against the original, and submit it to
gdb-patches@sourceware.cygnus.com. Then whoever is the maintainer of
the m68k code will look over it.
Jim
> It looks like I've found a small bug in insight.
> I've fixed it in on my PC but I would like to see it fixed in the main
> branch.
> I have no idea where to send this report and fix, so I'm posting it here.
>
> I have insight+dejagnu-weekly-20000412.tar.bz2 and Cygwin CD1.0
>
> I compiled it for --target=m68k-motorola-coff
>
> Then I tried to connect remotely to my SBC.
> Insight crashed.
> Crash happened in m68k-tdep.c in delta68_in_sigtramp:
>
> int delta68_in_sigtramp (pc, name)
> CORE_ADDR pc;
> char *name;
> {
> return strcmp (name, "_sigcode") == 0;
> }
>
> The reason -- pc was pointed to ROMmed RTOS rather than any program segment.
> So name parameter was NULL. Function strcmp crashed insight then.
> I've fixed the code and now it works fine.
> BTW, gdb 4.18 works fine, 'cuz it does not have this function.
>
>
> My solution:
>
> int delta68_in_sigtramp (pc, name)
> CORE_ADDR pc;
> char *name;
> {
> if (name) /* Serge's fix here */
> return strcmp (name, "_sigcode") == 0;
> return 0; /* Serge's fix here */
> }
>
>
>
>
>
>
prev parent reply other threads:[~2000-04-24 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-21 14:31 Serge Nikulin
2000-04-24 11:06 ` James Ingham [this message]
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=14596.36284.258460.711769@leda.cygnus.com \
--to=jingham@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=nikulin@actsw.amat.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).