question

Alan Jones avatar image
Alan Jones asked ·

libai debug symbols?

Hi all,

So, I'm getting a crash, which appears to have nothing to do with my shader (if you believe backtraces), but with no libai debug symbols it's hard to even hypothesize.

Are those available anywhere?

Here's what comes out if that leads anyone to ideas on how I'd track this down. Setting logging level to debug provides nothing either, it seems.

Cheers.

Alan.

signal caught: SIGSEGV -- Invalid memory reference

****
* Arnold 5.4.0.1 [197d4d5e] linux clang-5.0.0 oiio-2.1.0 osl-1.11.0 vdb-4.0.0 clm-1.0.3.513 rlm-12.4.2 optix-6.0.0 2019/09/12 15:05:20
* CRASHED in libai.so (0x00007fa3e8f62003) at 00:00:00, pixel (3593, -1)
* signal caught: SIGSEGV -- Invalid memory reference (address not mapped to object)
*
* backtrace:
* 0 0x00007fa3e8e846d4 [libai.so ] AiPromptADPDialog
* 1 0x00007fa4c467192f [libpthread.so.0] __funlockfile [:?]
>> 2 0x00007fa3e8f62003 [libai.so ]
* 3 0x00007fa3e8f62003 [libai.so ] AiPromptADPDialog
* 4 0x00007fa3e8da15d5 [libai.so ]
* 5 0x00007fa3e8c3a85e [libai.so ] AiPromptADPDialog
* 6 0x00007fa3e8f19e0d [libai.so ]
* 7 0x00007fa3e87b3d16 [libai.so ]
* 8 0x00007fa3e8db9e48 [libai.so ]
* 9 0x00007fa3e8db59bd [libai.so ]
* 10 0x00007fa3e8e8885d [libai.so ]
* 11 0x00007fa4c46664ce [libpthread.so.0] [pthread_create.c:?]
* 12 0x00007fa4c45952d2 [libc.so.6 ] clone [:?]
*
* loaded modules:
* 0x00007fa3e84be000 libai.so
* 0x00007fa4c465d000 libpthread.so.0
* 0x00007fa4c4496000 libc.so.6
*
* memory: VM 21528 MB, RSS 8280 MB, 2 page faults
****
Stack trace:
/opt/solidangle/mtoa/2019/plug-ins/../bin/libai.so(+0xaa4004) [0x7fa3e8f62004]
/opt/solidangle/mtoa/2019/plug-ins/../bin/libai.so(+0x8483ef) [0x7fa3e8d063ef]
/opt/solidangle/mtoa/2019/plug-ins/../bin/libai.so(+0x8e35d6) [0x7fa3e8da15d6]
/opt/solidangle/mtoa/2019/plug-ins/../bin/libai.so(+0x77c85f) [0x7fa3e8c3a85f]
/opt/solidangle/mtoa/2019/plug-ins/../bin/libai.so(+0xa5be0e) [0x7fa3e8f19e0e]
/opt/solidangle/mtoa/2019/plug-ins/../bin/libai.so(+0x2f5d17) [0x7fa3e87b3d17]
/opt/solidangle/mtoa/2019/plug-ins/../bin/libai.so(+0x8fbe49) [0x7fa3e8db9e49]
/opt/solidangle/mtoa/2019/plug-ins/../bin/libai.so(+0x8f79be) [0x7fa3e8db59be]
/opt/solidangle/mtoa/2019/plug-ins/../bin/libai.so(+0x9ca85e) [0x7fa3e8e8885e]
/usr/lib/libpthread.so.0(+0x94cf) [0x7fa4c46664cf]
clone

/usr/bin/maya2019: line 188: 7723 Segmentation fault (core dumped) /usr/autodesk/maya2019/bin/maya.bin

arnold
10 |600 characters needed characters left characters exceeded

Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

1 Answer

· Write an Answer
Stephen Blair avatar image
Stephen Blair answered ·

Does the crash trigger a CER report?

The backtrace itself can't be taken at face value...the symbols mentioned are wrong

3 comments
10 |600 characters needed characters left characters exceeded

Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Hi Stephen,

It didn't trigger a CER report. Apologies for the delay. It ended up appearing to be a corrupt scene. When I merged that scene into another, I was able to render without issue.

Though I'm assuming from what you've said there is no option for debug symbols? (for future issues)

Cheers,

Alan.

0 Likes 0 ·

Hi Alan

We don't distribute the debug symbols for Arnold. Your option would be to open a support case with us, and the devs will look at your crash.


Thanks


Stephen

0 Likes 0 ·
Alan Jones avatar image Alan Jones Stephen Blair ♦♦ ·

Hi Stephen,

Cool, thanks :) I won't bother for this one given I resolved it through the merge, but good to know if I hit it in future. Super rare, though - Arnold is solid.

Thanks again,

Alan.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Welcome to the Arnold Answers community.

This is the place for Arnold renderer users everywhere to ask and answer rendering questions, and share knowledge about using Arnold, Arnold plugins, workflows and developing tools with Arnold.

If you are a new user to Arnold Answers, please first check out our FAQ and User Guide for more information.

When posting questions, please be sure to select the appropriate Space for your Arnold plugin and include the plugin version you are using.

Please include images, scene and log files whenever possible as this helps the community answer your questions.

Instructions for generating full verbosity log files are available for MtoA, MaxtoA, C4DtoA, HtoA, KtoA, and Kick.

If you are looking for Arnold Documentation and Support please visit the Arnold Support site.

To try Arnold please visit the Arnold Trial page.

Bottom No panel present for this section.