From: Patrick Wollgast <patrick.wollgast@rub.de>
To: Kai Tietz <ktietz70@googlemail.com>,
"cmtice@google.com >> Caroline Tice" <cmtice@google.com>,
bkoz@gnu.org,
"jwakely@redhat.com >> Jonathan Wakely" <jwakely@redhat.com>,
iant@google.com
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [Ping] Port of VTV for Cygwin and MinGW
Date: Sun, 04 Jan 2015 20:10:00 -0000 [thread overview]
Message-ID: <54A99E34.2010202@rub.de> (raw)
In-Reply-To: <548876B5.70306@rub.de>
On 10.12.2014 17:37, Patrick Wollgast wrote:
> Ping.
>
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg03368.html
>
> On 27.11.2014 10:42, Patrick Wollgast wrote:
>> On 12.11.2014 19:40, Kai Tietz wrote:
>>> TerminateProcess is actually bad, as it doesn't call any of the atexit
>>> handlers. You simply nuke the process off. For cygwin this behavior
>>> is inacceptable. Why a classical abort, or a classical exit call
>>> cause for you that issues? It seems to me more related to some other
>>> thing you try to paper over by this.
>>>
>>
>> It turns out the test program made some trouble. I rewrote it to the
>> attached program (virtual_func_test_min_AW.cpp). I changed obstack.c and
>> vtv_rts.cc to the C-runtime functions. For testing I used a program just
>> containing an abort and all three tests in the attached test program.
>> The call stack, passed parameters and behavior matched at the crucial
>> parts (tested again on MinGW 32/64bit).
>>
>>>
>>>> Regarding the question, why I reimplemented mprotect, I also haven't
>>>> changed anything in the patch but answered the question.
>>>
>>> And this doesn't make it better. It is present in the static part of
>>> libgcc. Have you tried to declare it with extern "C" (for C++ case)
>>> and simply use it?
>>> Cygwin provides its own version too. So there seems to me no real
>>> need to re-implement it.
>>>
>>
>> You're right. I was stuck with the idea of importing it dynamically, but
>> changed it to extern "C" now.
>>
>> Regards,
>> Patrick
>>
next prev parent reply other threads:[~2015-01-04 20:10 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 11:04 Patrick Wollgast
2014-09-11 4:12 ` [Ping] " Patrick Wollgast
[not found] ` <CABtf2+RU7frwOXOX2FF8Tmfc6ssrpfFVj1Vuue4cZt19FpSWtQ@mail.gmail.com>
2014-09-12 22:44 ` Caroline Tice
2014-09-18 22:24 ` Patrick Wollgast
2014-09-23 6:16 ` Caroline Tice
2014-09-23 10:22 ` Jonathan Wakely
2014-09-24 22:25 ` Patrick Wollgast
2014-09-27 10:50 ` Kai Tietz
2014-10-09 13:56 ` Patrick Wollgast
2014-10-09 14:47 ` Kai Tietz
2014-10-16 10:23 ` Patrick Wollgast
2014-10-30 14:51 ` Patrick Wollgast
2014-11-12 16:23 ` Patrick Wollgast
2014-11-12 17:05 ` Kai Tietz
2014-11-12 17:47 ` Patrick Wollgast
2014-11-12 18:45 ` Kai Tietz
2014-11-27 9:59 ` Patrick Wollgast
2014-12-10 16:37 ` Patrick Wollgast
2015-01-04 20:10 ` Patrick Wollgast [this message]
2015-01-08 20:34 ` Patrick Wollgast
2015-01-12 18:32 ` Caroline Tice
2015-01-14 19:28 ` Ian Lance Taylor
2015-01-14 21:23 ` Patrick Wollgast
2015-01-14 23:56 ` Ian Lance Taylor
2015-01-15 8:34 ` Patrick Wollgast
2015-01-15 16:14 ` Ian Lance Taylor
2015-01-15 22:13 ` Patrick Wollgast
2015-01-28 14:04 ` Patrick Wollgast
2015-01-29 1:58 ` Caroline Tice
2015-01-29 18:16 ` Matthias Klose
2015-01-29 18:26 ` Matthias Klose
2015-01-29 18:28 ` Jonathan Wakely
2015-01-29 18:34 ` H.J. Lu
2015-01-29 18:59 ` H.J. Lu
2015-01-29 19:27 ` H.J. Lu
2015-01-29 18:30 ` H.J. Lu
2015-01-29 18:53 ` Matthias Klose
2015-01-29 19:39 ` Jakub Jelinek
2015-01-29 19:55 ` H.J. Lu
2015-01-29 20:01 ` Jakub Jelinek
2015-01-29 20:08 ` H.J. Lu
2015-01-29 19:28 ` Jakub Jelinek
2015-01-29 18:16 ` H.J. Lu
2015-01-29 18:22 ` H.J. Lu
2015-01-29 18:23 ` Caroline Tice
2015-02-09 12:32 ` Thomas Schwinge
2015-02-02 19:56 ` Patrick Wollgast
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=54A99E34.2010202@rub.de \
--to=patrick.wollgast@rub.de \
--cc=bkoz@gnu.org \
--cc=cmtice@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=jwakely@redhat.com \
--cc=ktietz70@googlemail.com \
--cc=libstdc++@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).