From: Doug Evans <dje@google.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org, Pedro Alves <pedro@codesourcery.com>
Subject: Re: [RFA] Fix gdbserver crash if using kill in remote connection to windows gdbserver
Date: Tue, 23 Jun 2009 17:11:00 -0000 [thread overview]
Message-ID: <e394668d0906231011r6c0784deuc5a8a2fb23349b0c@mail.gmail.com> (raw)
In-Reply-To: <003001c9f41e$3a294830$ae7bd890$@u-strasbg.fr>
On Tue, Jun 23, 2009 at 9:18 AM, Pierre Muller<muller@ics.u-strasbg.fr> wrote:
> GDB uses an internal fake pid (42000) for
> remote targets not supporting multi-processes,
> but send this fake pid to gdbserver when
> kill command is used with remote target.
>
> This made win32-low look for a inferior of
> pid 42000, which does not exist and created a crash
> in remove_process that was called with a NULL argument.
I thought gdb used 42000 for targets that don't have pids (e.g.
embedded targets).
It's kinda odd that gdb is using the magic 42000 on a target with pids.
Is that, perchance, the bug that needs fixing here?
next prev parent reply other threads:[~2009-06-23 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 16:18 Pierre Muller
2009-06-23 17:11 ` Doug Evans [this message]
2009-06-23 17:22 ` 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=e394668d0906231011r6c0784deuc5a8a2fb23349b0c@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=pedro@codesourcery.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