Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] gdbserver: Add qnx target
Date: Mon, 06 Jul 2009 16:49:00 -0000	[thread overview]
Message-ID: <200907061750.05522.pedro@codesourcery.com> (raw)
In-Reply-To: <4A521FD6.7040700@qnx.com>

On Monday 06 July 2009 17:01:26, Aleksandar Ristovski wrote:
> Pedro Alves wrote:

> > Are ldd.c's sources available?  :-)  If not, could you paste
> > that comment there too?
> 
> Comment from ldd.c pasted.

Thank you!  Looks nicer now.

> > On Wednesday 24 June 2009 19:50:39, Aleksandar Ristovski wrote
> >> +  i[34567]86-*-nto*)   srv_regobj=reg-i386.o
> >> +                       srv_tgtobj="nto-low.o nto-x86-low.o"
> >> +                       srv_qnx_LIBS=-lsocket
> >> +                       srv_qnx="yes"
> > 
> > Do you think the set of libs will change depending on the qnx
> > arch?  In other words, if you're adding a $srv_qnx, do you really
> > need a new srv_qnx_LIBS variable?
> 
> Unlikely. I just thought it was nicer. But in this patch I 
> removed it and -lsocket is now "hard-coded" in 
> configure.ac/configure.

Thanks.  I think that either your original patch (which I had
okayed), or the new one is fine --- while that version was middle
ground without the benefits of either.


> nto_inferior.exit_signo. Current code in nto-procfs.c 
> doesn't do that but it's a bug that results gdb reporting 
> "program exited normally" after program dies due to 
> unhandled signal.

Yeah.  You just might find out that the suggestion I had
given before would fix this cleanly.  :-)

> ChangeLog:
> 	Adding Neutrino gdbserver.
> 	* configure: Regenerated.
> 	* configure.ac: Add case for srv_qnx and set LIBS 
> accordingly..

              ^ spurious '.'

> 	* configure.srv (i[34567]86-*-nto*): New target.
> 	* nto-low.c, nto-low.h, nto-x86-low.c: New files.
> 	* remote-utils.c [__QNX__]: Include sys/iomgr.h

                                                       ^ missing '.'

> 	(nto_comctrl) [__QNX__]: New function.
> 	(enable_async_io, disable_async_io) [__QNX__]: Call 
> nto_comctrl.

Ok.  Please commit.


-- 
Pedro Alves


  reply	other threads:[~2009-07-06 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 15:05 Aleksandar Ristovski
2009-06-17 18:50 ` Aleksandar Ristovski
2009-06-20 16:01   ` Pedro Alves
2009-06-19 16:37 ` Pedro Alves
2009-06-19 16:42 ` Pedro Alves
2009-06-19 19:58   ` Aleksandar Ristovski
2009-06-20  0:01     ` Pedro Alves
2009-06-24 18:51       ` Aleksandar Ristovski
2009-06-30 12:11         ` Pedro Alves
2009-07-06 16:02           ` Aleksandar Ristovski
2009-07-06 16:49             ` Pedro Alves [this message]
2009-07-06 18:35               ` Aleksandar Ristovski

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=200907061750.05522.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=aristovski@qnx.com \
    --cc=gdb-patches@sourceware.org \
    /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