[llvm-dev] Pass segmentation fault after llvm_shutdown.

[Michael Platings via llvm-dev]

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

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
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

[Michael Platings via llvm-dev]

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 <[hidden email]> 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

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
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

[Michael Platings via llvm-dev]

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 <[hidden email]> 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

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
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
LLVM Developers mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

[Michael Platings via llvm-dev]

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 <[hidden email]> 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 <[hidden email]> 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

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
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
LLVM Developers mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

[Michael Platings via llvm-dev]

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 <[hidden email]> 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 <[hidden email]> 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

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
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
LLVM Developers mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev