Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] disassembly fixes
Date: Mon, 07 Apr 2003 14:26:00 -0000	[thread overview]
Message-ID: <16017.32156.807099.418676@localhost.redhat.com> (raw)
In-Reply-To: <20030407133223.GA5011@nevyn.them.org>

Daniel Jacobowitz writes:
 > On Fri, Apr 04, 2003 at 06:04:48PM -0500, Elena Zannoni wrote:
 > > 
 > > A few fixes for the new disassembler. I'll commit in a day or so.
 > > 
 > > 2003-04-04  Elena Zannoni  <ezannoni@redhat.com>
 > > 
 > > 	* disasm.c (dump_insns):  Move variables inside loop, or they will
 > >         be freed more than once, causing wild memory corruptions.
 > > 	(gdb_disassembly): Look for the substring "-thread",
 > >         instead of "-threads" in the target name, to make sure to find
 > >         the 'multi-thread' target.  Also, make sure we do the right thing 
 > >         with the "core" target.
 > 
 > While you're in there, any comments on:
 >   http://sources.redhat.com/ml/gdb/2003-02/msg00153.html
 > ?
 > 

Hmm, yes, I think that logic is a bit screwed up (it came from gdbtk,
and maybe there it was more appropriate), I have no objections if you
want to revisit the heuristics.  n hte meantime I would apply these
changes anyway because disassembly with core files and threaded
programs just doesn't work at all.

elena


 > -- 
 > Daniel Jacobowitz
 > MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-04-07 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 13:24 Elena Zannoni
2003-04-07 13:32 ` Daniel Jacobowitz
2003-04-07 14:26   ` Elena Zannoni [this message]
2003-04-07 18:50     ` Daniel Jacobowitz
2003-04-08  1:41       ` Elena Zannoni

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=16017.32156.807099.418676@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=drow@mvista.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