Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Monika Chaddha <monika@acmet.com>
Cc: gdb@sources.redhat.com
Subject: Re: break instruction in mips32
Date: Fri, 06 Aug 2004 17:15:00 -0000	[thread overview]
Message-ID: <4113BC54.2050900@avtrex.com> (raw)
In-Reply-To: <000001c47b9b$fc0c5330$5100a8c0@monika>

Monika Chaddha wrote:
> Hi All
> 
> As per specification of mips32, 'break' instruction should raise the
> Breakpoint Exception but gdb6.0 does not raise any break point
> exception.
> 
> As my understanding in GDB, Breakpoint implementation is done with the
> help of break instruction. Whenever user puts any breakpoint the actual
> instruction at that point is replaced by break instruction and the
> actual instruction is maintained in other list.
> 
> If I use break instruction in user program it does not raise any
> exception. Does mips32 not support 'BREAK' instruction in GDB.
> 
> Thanks & Regards
> Monika
> 

I am not sure what problems you are having with break, but recent
official versions of binutils and linux kernel had some "issues" WRT
break and the mips32 target.  I don't know how these effect GDB.

The problem is that "break 7" should be converted to SIGFPE, and other
break codes should result in SIGTRAP.  The problem I mention causes the
break 7 to incorrectly SIGTRAP.

This may be of no help, but I thought I would mention it anyhow.

David Daney.


  reply	other threads:[~2004-08-06 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06 10:01 Monika Chaddha
2004-08-06 17:15 ` David Daney [this message]
2004-08-09  8:58   ` Monika Chaddha

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=4113BC54.2050900@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=gdb@sources.redhat.com \
    --cc=monika@acmet.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