Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Joel Brobecker <brobecker@act-europe.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix compilation failure in hpux-thread.c under HPUX 11.00
Date: Mon, 01 Oct 2001 11:40:00 -0000	[thread overview]
Message-ID: <1011001183941.ZM18929@ocotillo.lan> (raw)
In-Reply-To: <20010928233120.A24896@act-europe.fr>

On Sep 28, 11:31pm, Joel Brobecker wrote:

>   As a side note, I tried to run the GDB I obtained and did not have
> much luck. Setting breakpoints seems ok, although I haven't double
> checked the pc addresses. However, when I try to run, GDB prints
> "Starting program ..." and then just sits there. The inferior is never
> spawned but I get 2 gdb processes for the price of one. I haven't had
> time to investigate more, and I'm not sure if this is because of my
> changes or not.

FWIW, I think this has been a problem for quite some time.  I did
actually try to build/run on HPUX at the time I was working on the
initial ptid_t changes (over a year ago now) and HPUX didn't work
then either.  It'd be really nice if someone would volunteer to be
the HPUX maintainer.

> Anyway, I'm attaching the patch, awaiting your comments. There is one
> static variable that was probably intended to be used as a cache. It was
> never assigned a value, so I deleted it for now. I could submit this
> obvious change as a separate patch if necessary.

I have no problem with this change being rolled into your present
patch.

> 2001-09-28  J. Brobecker <brobecker@gnat.com>
> 
> 	* hpux-thread.c: rewrite find_active_thread() and find_tcb()
> 	to use ptid_t, instead of overloading the thread and the pid
>         into the same 32-bit value. Make associated necessary adaptations.
>         Also remove unused variable cached_active_thread.

I've reviewed your patch and it looks right to me.  Since HPUX doesn't
have a maintainer, and you're fixing build problems, I think it's okay
for you to commit your changes.  (I think this is as close to saying
"Approved" as I can get without being the actual maintainer of the
code.)

Thanks,

Kevin


  reply	other threads:[~2001-10-01 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27  6:53 Joel Brobecker
2001-09-27 10:05 ` Kevin Buettner
2001-09-28 14:31   ` Joel Brobecker
2001-10-01 11:40     ` Kevin Buettner [this message]
2001-10-01 12:12       ` Andrew Cagney
2001-10-08 13:50       ` Joel Brobecker

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=1011001183941.ZM18929@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=brobecker@act-europe.fr \
    --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