Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Newman, Sarah R" <sarah.r.newman@lmco.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: RE: single stepping mips remote programs built with gcc 4.0
Date: Thu, 17 Nov 2005 22:39:00 -0000	[thread overview]
Message-ID: <5990BE666D0436419054489CDD9D505409667C95@emss01m10.us.lmco.com> (raw)

> Could you please build a debuggable GDB binary, and trace through
> mips32_next_pc?  It looks like it should handle the 'j' instruction
> just fine:
> 
>         case 2:         /* J */
>         case 3:         /* JAL */
>           {
>             unsigned long reg;
>             reg = jtype_target (inst) << 2;
>             /* Upper four bits get never changed... */
>             pc = reg + ((pc + 4) & 0xf0000000);
>           }
>           break;
> 
> J and JAL share a format, so this should be correct.  It's as if the
> value GDB is extracting for the instruction is incorrect.
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 

I built it with the default options, that good enough? Something like
"-g -O2" it seems.

I doubt that mips32_next_pc is getting compiled in because I can set a
breakpoint at mips_next_pc but not mips32_next_pc.  
mips_software_single_step never gets called in this sequence, should it
be? 


             reply	other threads:[~2005-11-17 22:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 22:39 Newman, Sarah R [this message]
2005-11-17 22:48 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2005-11-23  3:09 Newman, Sarah R
2005-11-22 20:00 Newman, Sarah R
2005-11-22 19:48 Newman, Sarah R
2005-11-22  5:26 Newman, Sarah R
2005-11-22 19:24 ` Daniel Jacobowitz
2005-11-23  0:50 ` Jim Blandy
2005-11-17 20:13 Newman, Sarah R
2005-11-17 20:23 ` Daniel Jacobowitz

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=5990BE666D0436419054489CDD9D505409667C95@emss01m10.us.lmco.com \
    --to=sarah.r.newman@lmco.com \
    --cc=drow@false.org \
    --cc=gdb@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