llvm dev - May 2018 - Pass segmentation fault after llvm_shutdown.

I ran into a similar problem a while ago; see 
https://reviews.llvm.org/D30107 and https://reviews.llvm.org/D33515 .  
You get the unusual stack trace because it's trying to call a destructor 
in shared library which was already unloaded.

I thought we had fixed that, but maybe not?  Looking again, it looks 
like the patch got reverted and I didn't notice.

-Eli

On 5/14/2018 10:18 PM, Simone Atzeni via llvm-dev wrote:
> This is the correct path to the pass: 
>
https://github.com/PRUNERS/sword/blob/master/lib/Transforms/Instrumentation/InstrumentParallel.cpp
>
> On Mon, May 14, 2018 at 10:06 PM, Simone Atzeni <simone.at at gmail.com 
> <mailto:simone.at at gmail.com>> wrote:
>
>     Hi all,
>
>     I was porting my pass from LLVM 4.0 to 6.0 and I am getting a
>     segmentation fault.
>     I was able to obtain only the info below from GDB.
>
>     I tried to debug with some printf and the runOnFunction runs
>     correctly.
>     Any idea/suggestion about what is going on?
>
>     The source code of the pass is here:
>     https://github.com/PRUNERS/sword/blob/master/lib/Sword.cpp
>     <https://github.com/PRUNERS/sword/blob/master/lib/Sword.cpp>
>
>     Any help is much appreciated,
>     Thanks!
>     Simone
>
>     #0  0x00007f1d93735170 in ?? ()
>     #1  0x00000000017d2b96 in
>    
llvm::object_deleter<llvm::SmallVector<std::pair<llvm::PassManagerBuilder::ExtensionPointTy,
>     std::function<void (llvm::PassManagerBuilder const&,
>     llvm::legacy::PassManagerBase&)> >, 8u> >::call(void*)
()
>     #2  0x0000000001b0e5e9 in llvm::llvm_shutdown() ()
>     #3  0x00000000008d8077 in main ()
>
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180515/450fe46a/attachment-0001.html>

It's working with trunk though. Do you think the patch will end up in
6.0.1?

Thanks.
Simone

On Tue, May 15, 2018 at 11:18 AM, Friedman, Eli <efriedma at
codeaurora.org>
wrote:
> I ran into a similar problem a while ago; see https://reviews.llvm.org/
> D30107 and https://reviews.llvm.org/D33515 .  You get the unusual stack
> trace because it's trying to call a destructor in shared library which
was
> already unloaded.
>
> I thought we had fixed that, but maybe not?  Looking again, it looks like
> the patch got reverted and I didn't notice.
>
> -Eli
>
>
> On 5/14/2018 10:18 PM, Simone Atzeni via llvm-dev wrote:
>
> This is the correct path to the pass: https://github.com/
> PRUNERS/sword/blob/master/lib/Transforms/Instrumentation/
> InstrumentParallel.cpp
>
> On Mon, May 14, 2018 at 10:06 PM, Simone Atzeni <simone.at at
gmail.com>
> wrote:
>
>> Hi all,
>>
>> I was porting my pass from LLVM 4.0 to 6.0 and I am getting a
>> segmentation fault.
>> I was able to obtain only the info below from GDB.
>>
>> I tried to debug with some printf and the runOnFunction runs correctly.
>> Any idea/suggestion about what is going on?
>>
>> The source code of the pass is here: https://github.com/PRUNE
>> RS/sword/blob/master/lib/Sword.cpp
>>
>> Any help is much appreciated,
>> Thanks!
>> Simone
>>
>> #0  0x00007f1d93735170 in ?? ()
>> #1  0x00000000017d2b96 in llvm::object_deleter<llvm::Sma
>> llVector<std::pair<llvm::PassManagerBuilder::ExtensionPointTy,
>> std::function<void (llvm::PassManagerBuilder const&,
>> llvm::legacy::PassManagerBase&)> >, 8u> >::call(void*)
()
>> #2  0x0000000001b0e5e9 in llvm::llvm_shutdown() ()
>> #3  0x00000000008d8077 in main ()
>>
>>
>
>
> _______________________________________________
> LLVM Developers mailing listllvm-dev at
lists.llvm.orghttp://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
> --
> Employee of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180516/7314c723/attachment.html>

I have no idea what changed between 6.0 and trunk, so probably not?

-Eli

On 5/16/2018 10:23 PM, Simone Atzeni wrote:
> It's working with trunk though. Do you think the patch will end up in 
> 6.0.1?
>
> Thanks.
> Simone
>
> On Tue, May 15, 2018 at 11:18 AM, Friedman, Eli 
> <efriedma at codeaurora.org <mailto:efriedma at
codeaurora.org>> wrote:
>
>     I ran into a similar problem a while ago; see
>     https://reviews.llvm.org/D30107 <https://reviews.llvm.org/D30107>
>     and https://reviews.llvm.org/D33515
>     <https://reviews.llvm.org/D33515> .  You get the unusual stack
>     trace because it's trying to call a destructor in shared library
>     which was already unloaded.
>
>     I thought we had fixed that, but maybe not?  Looking again, it
>     looks like the patch got reverted and I didn't notice.
>
>     -Eli
>
>
>     On 5/14/2018 10:18 PM, Simone Atzeni via llvm-dev wrote:
>>     This is the correct path to the pass:
>>    
https://github.com/PRUNERS/sword/blob/master/lib/Transforms/Instrumentation/InstrumentParallel.cpp
>>    
<https://github.com/PRUNERS/sword/blob/master/lib/Transforms/Instrumentation/InstrumentParallel.cpp>
>>
>>     On Mon, May 14, 2018 at 10:06 PM, Simone Atzeni
>>     <simone.at at gmail.com <mailto:simone.at at
gmail.com>> wrote:
>>
>>         Hi all,
>>
>>         I was porting my pass from LLVM 4.0 to 6.0 and I am getting a
>>         segmentation fault.
>>         I was able to obtain only the info below from GDB.
>>
>>         I tried to debug with some printf and the runOnFunction runs
>>         correctly.
>>         Any idea/suggestion about what is going on?
>>
>>         The source code of the pass is here:
>>         https://github.com/PRUNERS/sword/blob/master/lib/Sword.cpp
>>        
<https://github.com/PRUNERS/sword/blob/master/lib/Sword.cpp>
>>
>>         Any help is much appreciated,
>>         Thanks!
>>         Simone
>>
>>         #0  0x00007f1d93735170 in ?? ()
>>         #1  0x00000000017d2b96 in
>>        
llvm::object_deleter<llvm::SmallVector<std::pair<llvm::PassManagerBuilder::ExtensionPointTy,
>>         std::function<void (llvm::PassManagerBuilder const&,
>>         llvm::legacy::PassManagerBase&)> >, 8u>
>::call(void*) ()
>>         #2  0x0000000001b0e5e9 in llvm::llvm_shutdown() ()
>>         #3  0x00000000008d8077 in main ()
>>
>>
>>
>>
>>     _______________________________________________
>>     LLVM Developers mailing list
>>     llvm-dev at lists.llvm.org <mailto:llvm-dev at
lists.llvm.org>
>>     http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>     <http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
>
>
>     -- 
>     Employee of Qualcomm Innovation Center, Inc.
>     Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
Linux Foundation Collaborative Project
>
>
-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180517/570f5d88/attachment.html>