Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Fred Fish <fnf@intrinsity.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Don't clobber info->mach in gdb_print_insn_mips
Date: Mon, 23 Jun 2003 21:40:00 -0000	[thread overview]
Message-ID: <3EF772BD.3020100@redhat.com> (raw)
In-Reply-To: <20030623211823.AEF0E2F2F2C@beeville.vert.intrinsity.com>

> info->mach field being clobbered by gdb_print_insn_mips.  The attached
>> > patch fixes it, though I'm not sure if this is the correct solution.
> 
>> 
>> What happens if info->mach is never set?  gdb_disassemble_info should 
>> have already set it correctly.
> 
> 
> Yes, gdb_disassemble_info sets it correctly, and then gdb_print_insn_mips
> clobbers it back to zero.  Here is a typescript showing the order that
> various functions are called.
> 
> Without my patch, gdb_disassemble_info sets it to a correct value,
> gdb_print_insn_mips clobbers it back to zero, and then eventually
> choose_arch_by_number gets called with mach==0 (my typescript shows
> 10611501, the expected value for my port, since I have my patch
> installed).  Since choose_arch_by_number then returns zero,
> the code in set_default_mips_dis_options that sets mips_isa
> never gets executed:

So you're ok if I delete that bit of gdb_print_insn_mips?

Andrew



  reply	other threads:[~2003-06-23 21:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 14:14 Fred Fish
2003-06-23 20:38 ` Andrew Cagney
2003-06-23 21:39   ` Fred Fish
2003-06-23 21:40     ` Andrew Cagney [this message]
2003-06-24  0:51       ` Fred Fish
2003-06-25 21:47         ` Andrew Cagney
2003-06-26 18:00           ` Andrew Cagney

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=3EF772BD.3020100@redhat.com \
    --to=ac131313@redhat.com \
    --cc=fnf@intrinsity.com \
    --cc=gdb-patches@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