From: "Monika Chaddha" <monika@acmet.com>
To: "'Michael Chastain'" <mec.gnu@mindspring.com>, <gdb@sources.redhat.com>
Subject: RE: debugger 6.2.1 misfeatures
Date: Sat, 11 Sep 2004 09:59:00 -0000 [thread overview]
Message-ID: <004501c497e5$a53cd9b0$5100a8c0@monika> (raw)
In-Reply-To: <4142590A.nailCR31XGTUA@mindspring.com>
Is it necessary to send test cases with the bug? I had sent the
following bug with patch some days ago but didn't get any response
regarding this. I don't have any test case till now to prove this bug as
it can be test only for remote target during tracing.
What should I do? Pls help.
Thanks & Regards
Monika
Defect report:-
-------------
File
-----
/src/sim/mips/m16.igen
Defects
--------
1. Mnemonic for CMP instruction is putted as
"sltiu r<TRX>, r<TRY>"
While it should be as
"cmp r<TRX>, r<TRY>"
2. Mnemonic for CMPI instruction is putted as
"sltiu r<TRX>, <IMMED>"
While it should be as
"cmpi r<TRX>, <IMMED>"
Patch
-----
GDB Version no: 6.0
File: /src/sim/mips/m16.igen
11101,3.RX,3.RY,01010:RR:16::CMP
-"sltiu r<TRX>, r<TRY>"
+"cmp r<TRX>, r<TRY>"
*mips16:
*vr4100:
{
do_xor (SD_, TRX, TRY, T8IDX);
}
01110,3.RX,8.IMMED:RI:16::CMPI
-"sltiu r<TRX>, <IMMED>"
+"cmpi r<TRX>, <IMMED>"
*mips16:
*vr4100:
{
do_xori (SD_, TRX, T8IDX, IMMED);
}
>-----Original Message-----
>From: gdb-owner@sources.redhat.com
[mailto:gdb-owner@sources.redhat.com] On
>Behalf Of Michael Chastain
>Sent: Saturday, September 11, 2004 7:17 AM
>To: gdb@sources.redhat.com; esp5@pge.com
>Subject: Re: debugger 6.2.1 misfeatures
>
>Sounds like a bug to me.
>
>Generally for a bug, we need:
>
> the gdb version
> the host operating system version
> the target operating system version (if it's not the same as the
host)
> a typescript of the whole gdb session showing the bug
> (use the 'script' command)
> some info about the inferior program:
> what language it's written in
> the exact compiler name and compiler version that it was built with
>
>Then if somebody picks up the bug, they're likely to come back with
>more questions. The point at this stage is not to identify the bug,
>but just to throw enough information over the fence so that the
>gdb engineer can *reproduce* the bug.
>
>If it worked with a previous version of gdb, that's good to know.
>
>It's really great if you can supply a small test program
>(source + binary) that demonstrates the bug.
>
>And some bug reports are successful and get fixed, and some aren't
>and don't.
>
>Michael Chastain
next prev parent reply other threads:[~2004-09-11 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 0:05 Edward Peschko
2004-09-11 1:46 ` Michael Chastain
2004-09-11 9:59 ` Monika Chaddha [this message]
2004-09-11 15:52 ` Michael Chastain
2004-09-13 7:01 ` Monika Chaddha
2004-09-11 16:26 ` Joel Brobecker
2004-09-15 6:37 ` Joel Brobecker
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='004501c497e5$a53cd9b0$5100a8c0@monika' \
--to=monika@acmet.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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