Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@cygnus.com>
To: "Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: symfile.c: Fix for GDB crash when rereading symbols
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <38CE8221.241F@cygnus.com> (raw)
Message-ID: <20000401000000.hGgNPFV0ruRVaQkZ8MtMvJpqvt66OR7zonj_Wqp5lCc@z> (raw)
In-Reply-To: <200003141046.LAA08835@reisser.regent.e-technik.tu-muenchen.de>

Peter.Schauer wrote:
> 
> symfile.c:reread_symbols does not clear the new msymbol hash tables
> in the objfile, causing stale pointers and a GDB crash during the
> reread.exp test on Solaris.
> 
> Here is a fix:

Great!  I was just noticing that failure last night.
Thanks!
From ac131313@cygnus.com Sat Apr 01 00:00:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: jtc@redback.com
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: i386/tm-nsbd.h, i386/nm-nbsd.h
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <38D7F5FC.8D45CBAF@cygnus.com>
References: <5m66uggiur.fsf@jtc.redbacknetworks.com>
X-SW-Source: 2000-q1/msg00877.html
Content-length: 375

"J.T. Conklin" wrote:
> 
> I submit the enclosed patch for approval.  These changes enable
> floating point register support on NetBSD/i386.
> 
>         --jtc
> 
> 2000-03-21  J.T. Conklin  <jtc@redback.com>
> 
>         * i386/tm-nbsd.h (NUM_REGS): Removed.
>         (HAVE_I387_REGS): Defined.
>         * i386/nm-nbsd.h (FLOAT_INFO): Removed.

Approved (thanks).
	Andrew
From rearnsha@arm.com Sat Apr 01 00:00:00 2000
From: Richard Earnshaw <rearnsha@arm.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: rearnsha@arm.com
Subject: Re: ARM patch -- extra info about cpsr register 
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <200003281047.LAA02722@cam-mail2.cambridge.arm.com>
References: <38DFB300.B82108A@cygnus.com>
X-SW-Source: 2000-q1/msg01082.html
Content-length: 1041

> Hi Richard,
> 
> Thanks for the submission.  However, we are using something else to show register bits nowadays.  It uses the
> REGISTER_VIRTUAL_TYPE and we build a type for the register with bitfields so normal gdb processing (and the GUI) can
> show the bits and allow the user to set a specific bit by name (without having to know its position by heart).
> 
> I am sorting out some details and tracking down a bug in gdb before making it available.  My code is for another
> processor but it will be very easy to adapt it for ARM.  If you fell like helping, as soon as I have a final version I
> can point you to the right pieces of code.
> 
> Hope you are not too disappointed.

Not at all.  It's not the implementation that's important; it's that the 
information be decoded for the user.  Mapping a hex number to a set of 
mnemonics is something a computer is good and and a human is not.   If 
your version allows the user to set the register mnemonically as well, 
then all the better.

Please keep me posted on your patch.

R.



       reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200003141046.LAA08835@reisser.regent.e-technik.tu-muenchen.de>
2000-03-14 10:20 ` Michael Snyder [this message]
2000-04-01  0:00   ` Michael Snyder
2000-04-01  0:00 ` Michael Snyder

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=38CE8221.241F@cygnus.com \
    --to=msnyder@cygnus.com \
    --cc=Peter.Schauer@regent.e-technik.tu-muenchen.de \
    --cc=gdb-patches@sourceware.cygnus.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