Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Kris Warkentin <kewarken@qnx.com>
Cc: "Gdb-Patches@Sources.Redhat.Com" <gdb-patches@sources.redhat.com>
Subject: Re: [patch] Bring QNX Neutrino support forward.
Date: Wed, 24 Mar 2004 14:35:00 -0000	[thread overview]
Message-ID: <40619CB3.90001@gnu.org> (raw)
In-Reply-To: <40618FCD.5010802@qnx.com>

> Andrew Cagney wrote:
> 
>>> Some of this stuff is cosmetic/convenience.  I made the macros for my nto_target structure testable and moved the comments into the structure where they're more useful.
>>>
>>> A few things had to do with initializers.  Some of the signal handling stuff didn't work because other _init functions hadn't been called so I moved them out to where they could be called when the osabi is initialized.
>>
>>
>>
>> BTW, what was the race condition?
> 
> 
> The _initialize_* functions were being called in a different order than previously so all my signal initialization stuff was breaking when I put it into my _init* funcs.  It was a while ago I changed it (haven't been working on FSF gdb recently) but I believe it was target_signal_from_name....

Ulgh, one of those (if you remember any more details :-).  I'll need to 
investigate - these race conditions are a royal pain.

>>> I added osabi and core sniffers.  Some is practical, some is future-proofing.  If we start supporting multiple targets, I'm going to want to be able to swap our various target processors support in and out.  The is_nto_target type stuff can be made more interesting later to do things like check to see if the remote host processor matches the binary abi and such.
>>
>>
>>
>> You should also be able to kill off regset_core_fns, it's been superseeded by regsets (which reminds me ....).
> 
> 
> Must have not seen that thread.  I'll look into it.

There are no deprecated markers so there's no hint.  A grep of 
add_core_fns reveals that the i386/amd64 and GNU/Linux PPC do not make 
the call so I'm pretty sure that I'm not talking theory here (notably 
32x64 GNU/Linux debugging works on those systems -- that needs regsets).

Andrew



  reply	other threads:[~2004-03-24 14:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 21:18 Kris Warkentin
2004-03-23 23:21 ` Andrew Cagney
2004-03-24 13:38   ` Kris Warkentin
2004-03-24 14:35     ` Andrew Cagney [this message]
2004-03-24 16:32       ` Kris Warkentin
2004-03-25 17:22         ` Kris Warkentin
2004-03-26  3:43           ` Andrew Cagney
2004-03-31 22:21 ` Daniel Jacobowitz
2004-04-01 14:59   ` Kris Warkentin
2004-04-01 15:04     ` Daniel Jacobowitz

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=40619CB3.90001@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kewarken@qnx.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