Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: pthreads debug with gdbserver
Date: Sun, 21 Nov 2004 01:11:00 -0000	[thread overview]
Message-ID: <20041121011142.GA27723@nevyn.them.org> (raw)
In-Reply-To: <m3y8gw588f.fsf@igel.m5r.de>

On Sun, Nov 21, 2004 at 01:57:52AM +0100, Andreas Schwab wrote:
> Daniel Jacobowitz <drow@false.org> writes:
> 
> > Take a look at the source code to gdbserver.  Andreas, now I remember
> > why I enabled thread_db support on a per-target basis - there are other
> > support routines that have to be written.
> 
> Here is the gdbserver support for thread_db and regsets on m68k-linux.
> OK?
> 
> Andreas.
> 
> 2004-11-21  Andreas Schwab  <schwab@suse.de>
> 
> 	* linux-m68k-low.c (m68k_num_gregs): Define.
> 	(m68k_fill_gregset, m68k_store_gregset, m68k_fill_fpregset)
> 	(m68k_store_fpregset, target_regsets) [HAVE_LINUX_REGSETS]: New.
> 	(m68k_breakpoint, m68k_breakpoint_len, m68k_get_pc, m68k_set_pc)
> 	(m68k_breakpoint_at): New.  Add to the_low_target.
> 
> 	* configure.srv (m68*-*-linux*): Set srv_linux_regsets and
> 	srv_linux_thread_db to yes.

Yes, this is OK.  Thanks a lot!

-- 
Daniel Jacobowitz


      reply	other threads:[~2004-11-21  1:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200411191233.22357.vladimir.vorobyov@iss.org.ua>
     [not found] ` <200411191641.15822.vladimir.vorobyov@iss.org.ua>
     [not found]   ` <20041120013220.GB27485@nevyn.them.org>
     [not found]     ` <200411201427.13557.vladimir.vorobyov@iss.org.ua>
     [not found]       ` <20041120164209.GA15174@nevyn.them.org>
2004-11-21  0:58         ` Andreas Schwab
2004-11-21  1:11           ` Daniel Jacobowitz [this message]

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=20041121011142.GA27723@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /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