This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v7 1/4] gdb: Add OpenRISC or1k and or1knd target support


On Mon, Jun 12, 2017 at 10:45:15AM +0100, Yao Qi wrote:
> Stafford Horne <shorne@gmail.com> writes:
> 
> > I tried to look into this, but it looks liek we do need
> > set_gdbarch_print_insn ().   If not starting gdb hits this error in
> > gdbarch.c verify_gdbarch().
> >
> > ...
> >   if (gdbarch->print_insn == 0)
> >     log.puts ("\n\tprint_insn");
> 
> These lines were removed by my commit
> 39503f82427e22ed8e04d986ccdc8562091ec62e (Delegate opcodes to select
> disassembler in GDB) on May 24th.
> 
> -  if (gdbarch->print_insn == 0)
> -    log.puts ("\n\tprint_insn");
> +  /* Skip verify of print_insn, invalid_p == 0 */
> 
> > ...
> >
> >   if (!log.empty ())
> >     internal_error (__FILE__, __LINE__,
> > 		    _("verify_gdbarch: the following are invalid ...%s"),
> > 		    log.c_str ());
> > ...
> >
> > Is the automatic selecting of `print_insn` something new?  My patch is
> > based on yesterdays master branch of http://sourceware.org/git/binutils-gdb.git.
> 
> Looks your gdbarch.c is out of date.

Thanks, I see it now.

-Stafford


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]