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

Andrew Cagney wrote:

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

I'll just temporarily move the signal setup stuff to my _init....okay.  
It's this line of code in my init function:

signal_stop_update (target_signal_from_name ("SIG45"), 0);

The array 'signal_stop' in signal_stop_update has not been initialized 
so we blow up.

> 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).


I think I'm failing to understand you here.  If I don't use the 
regset_core_functions, how do I sniff out a Neutrino core using

    if (bfd_get_section_by_name (abfd, ".qnx_core_info"))
       you_have_core();
?

Should I be adding that to the default_core_sniffer?

cheers,

Kris


  reply	other threads:[~2004-03-24 16:32 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
2004-03-24 16:32       ` Kris Warkentin [this message]
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=4061B878.6010209@qnx.com \
    --to=kewarken@qnx.com \
    --cc=cagney@gnu.org \
    --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