thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Young (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (THRIFT-4291) Two different thrift interface in the same project causes run time asserts
Date Mon, 02 Oct 2017 09:19:00 GMT

     [ https://issues.apache.org/jira/browse/THRIFT-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Peter Young closed THRIFT-4291.
-------------------------------
    Resolution: Fixed

> Two different thrift interface in the same project causes run time asserts
> --------------------------------------------------------------------------
>
>                 Key: THRIFT-4291
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4291
>             Project: Thrift
>          Issue Type: Question
>          Components: C++ - Library
>    Affects Versions: 0.9.3
>         Environment: VS2013 Windows 10 32-bit
>            Reporter: Peter Young
>              Labels: newbie
>
> I am developing a thrift-based interface to manage some external components of my companies
workflow product. The product is an executable plus several dlls to provide functionality.
> I already have a device-specific Thrift Interface and 'core' thrift source code (TApplicationException.cpp,
etc) in the .exe in order to communicate with a customers device. The Thrift source/header
files are included directly into the Server. I did have the 'core' Thrift code in a static
library but moved the code in directly as I try to resolve this issue.
> I need to include the same 'core' code plus a different Thrift interface (to drive our
external components) into a DLL which the Server will load.
> I can build and link the DLL, but the Server generates assert after assert trying to
load the DLL in order to debug it. I have narrowed down the issue to the inclusion of BoostMonitor.cpp
& BoostMutex.cpp. Just having them built into the project, even if they are not used,
is triggering the issue.I cannot include one without the other in order to narrow this down
any further.
> Any suggestions as to what could be causing the asserts (generated by mfc120d.dll)?
> Thanks,
> Pete Young



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message