From: Danny Backx <danny.backx@scarlet.be>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: Build question
Date: Sat, 12 Sep 2009 14:53:00 -0000 [thread overview]
Message-ID: <1252767271.8804.41.camel@pavilion> (raw)
In-Reply-To: <200909111622.34265.pedro@codesourcery.com>
On Fri, 2009-09-11 at 16:22 +0100, Pedro Alves wrote:
> DebugActiveProcessStop = GETPROCADDRESS (dll, DebugActiveProcessStop);
> DebugSetProcessKillOnExit = GETPROCADDRESS (dll, DebugSetProcessKillOnExit);
>
> if (DebugSetProcessKillOnExit == NULL
> || DebugActiveProcessStop == NULL)
> return -1;
>
> Try checking if DebugActiveProcessStop is non-NULL here on
> your CE >= 6.0 device, and tweak this code to make it possible to detach
> with DebugActiveProcessStop even if we don't support
> DebugSetProcessKillOnExit.
Apologies, I forgot to answer this part of the mail.
\network\x86> testapi coredll DebugActiveProcessStop
coredll implements DebugActiveProcessStop (0x4003F4F0)
\network\x86> testapi coredll DebugSetProcessKillOnExit
coredll implements DebugSetProcessKillOnExit (0x4003F510)
\network\x86>
My testapi utility basically does what you asked (LoadLibrary -
GetProcAddress - print the result).
I'll look into this.
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
next prev parent reply other threads:[~2009-09-12 14:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1250803105.11282.96.camel@pavilion>
[not found] ` <m3fxbl2jib.fsf@fleche.redhat.com>
[not found] ` <83d46pgjkq.fsf@gnu.org>
[not found] ` <1250877901.11282.116.camel@pavilion>
[not found] ` <83ab1tgh9h.fsf@gnu.org>
[not found] ` <1250880746.11282.128.camel@pavilion>
[not found] ` <m3r5v425lu.fsf@fleche.redhat.com>
[not found] ` <1250931899.11282.142.camel@pavilion>
[not found] ` <83skfkfa4n.fsf@gnu.org>
[not found] ` <1251095160.16357.352.camel@pavilion>
[not found] ` <1251828295.6106.119.camel@pavilion>
[not found] ` <83zl9e8nro.fsf@gnu.org>
[not found] ` <1251835928.6106.124.camel@pavilion>
[not found] ` <83vdk281xb.fsf@gnu.org>
[not found] ` <1252143311.6106.252.camel@pavilion>
2009-09-05 16:12 ` Eli Zaretskii
2009-09-07 22:12 ` Joel Brobecker
2009-09-08 15:53 ` Danny Backx
2009-09-08 20:13 ` Danny Backx
2009-09-09 19:57 ` Tom Tromey
2009-09-11 14:41 ` Danny Backx
2009-09-11 15:22 ` Pedro Alves
2009-09-11 15:28 ` Pedro Alves
2009-09-12 14:48 ` Danny Backx
2009-09-12 15:03 ` Pedro Alves
2009-09-12 16:58 ` Danny Backx
2009-09-13 16:10 ` Pedro Alves
2009-09-13 18:07 ` Danny Backx
2009-09-12 14:53 ` Danny Backx [this message]
2009-09-13 9:30 ` Danny Backx
2009-09-13 16:04 ` Joel Brobecker
2009-09-14 18:03 ` Tom Tromey
2009-09-14 18:25 ` 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=1252767271.8804.41.camel@pavilion \
--to=danny.backx@scarlet.be \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@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