Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org,  Eli Zaretskii <eliz@gnu.org>
Subject: Re: [djgpp/commit] Fix go32_pid_to_str and go32_thread_alive
Date: Fri, 01 May 2009 10:19:00 -0000	[thread overview]
Message-ID: <200905011118.51917.pedro@codesourcery.com> (raw)
In-Reply-To: <834ow5dypg.fsf@gnu.org>

On Friday 01 May 2009 09:17:15, Eli Zaretskii wrote:

> 2009-05-01  Eli Zaretskii  <eliz@gnu.org>
> 
> 	* go32-nat.c (go32_pid_to_str): Call normal_pid_to_str instead of
> 	printing a bogus "Thread <main>".

I thought that the inferior's PID on DJGPP is always the
fake SOMEPID (42), an internal implementation detail, that we'd
never want to show to the user, but, normal_pid_to_str will
print "process 42" here.  Isn't that bogus as well?

> 	(go32_thread_alive): Don't return 1 for null_ptid.

Interesting.  This may be masking some other problem.  How
did you get here with inferior_ptid == null_ptid?  AFAICS,
when the inferior exits or is killed, the go32_ops target
is unpushed.

> 
> Index: gdb/go32-nat.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/go32-nat.c,v
> retrieving revision 1.71
> diff -u -r1.71 go32-nat.c
> --- gdb/go32-nat.c	19 Apr 2009 18:29:33 -0000	1.71
> +++ gdb/go32-nat.c	1 May 2009 08:12:36 -0000
> @@ -870,15 +870,13 @@
>  static int
>  go32_thread_alive (struct target_ops *ops, ptid_t ptid)
>  {
> -  return 1;
> +  return !ptid_equal (inferior_ptid, null_ptid);
>  }
>  
>  static char *
>  go32_pid_to_str (struct target_ops *ops, ptid_t ptid)
>  {
> -  static char buf[64];
> -  xsnprintf (buf, sizeof buf, "Thread <main>");
> -  return buf;
> +  return normal_pid_to_str (ptid);
>  }
>  
>  static void
> 

-- 
Pedro Alves


  reply	other threads:[~2009-05-01 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01  8:18 Eli Zaretskii
2009-05-01 10:19 ` Pedro Alves [this message]
2009-05-01 12:57   ` Eli Zaretskii
2009-05-01 13:32     ` Pedro Alves

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=200905011118.51917.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=eliz@gnu.org \
    --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