Folks,

can someone of you with a keen Linux eye and some valgrind knack give me
a hand, and check why the current POV-Ray master branch bombs during the
"make check" step (more specifically while parsing the "biscuit.pov"
advanced sample scene) on Ubuntu?

Post a reply to this message

hi,

On 05/05/2016 15:58, clipka wrote:
> can someone of you with a keen Linux eye and some valgrind knack give me
> a hand, and check why the current POV-Ray master branch bombs during the
> "make check" step (more specifically while parsing the "biscuit.pov"
> advanced sample scene) on Ubuntu?

see attached (text) file, hth.

jr.

Post a reply to this message

Attachments:
Download 'pov-valg.txt' (13 KB)

Am 05.05.2016 um 21:10 schrieb jr:
> hi,
> 
> On 05/05/2016 15:58, clipka wrote:
>> can someone of you with a keen Linux eye and some valgrind knack give me
>> a hand, and check why the current POV-Ray master branch bombs during the
>> "make check" step (more specifically while parsing the "biscuit.pov"
>> advanced sample scene) on Ubuntu?
> 
> see attached (text) file, hth.

Thanks for your effort; unfortunately, the valgrind output is of little
use to me without human-readable stack trace information; can you try
again with a version of POV-Ray configured to include debug information?

Post a reply to this message

Le 05/05/2016 21:22, clipka a écrit :
> Am 05.05.2016 um 21:10 schrieb jr:
>> hi,
>>
>> On 05/05/2016 15:58, clipka wrote:
>>> can someone of you with a keen Linux eye and some valgrind knack give me
>>> a hand, and check why the current POV-Ray master branch bombs during the
>>> "make check" step (more specifically while parsing the "biscuit.pov"
>>> advanced sample scene) on Ubuntu?
>>
>> see attached (text) file, hth.
> 
> Thanks for your effort; unfortunately, the valgrind output is of little
> use to me without human-readable stack trace information; can you try
> again with a version of POV-Ray configured to include debug information?
> 

Enjoy the attached file

Post a reply to this message

Attachments:
Download 'debug.txt' (9 KB)

Am 05.05.2016 um 21:40 schrieb Le_Forgeron:

> Enjoy the attached file

Thanks.

Fortunately that looks indeed related to the most recent changes I made ;)

Post a reply to this message

Am 05.05.2016 um 21:48 schrieb clipka:
> Am 05.05.2016 um 21:40 schrieb Le_Forgeron:
> 
>> Enjoy the attached file
> 
> Thanks.
> 
> Fortunately that looks indeed related to the most recent changes I made ;)

Actually no, it wasn't really linked to the "bulk" of the changes at all
(which were about making global variables accessible even if the same
identifier is also used locally) -- but I introduced a new keyword, and
pushed the updated `reservedwords.h` to the repo but not the matching
`reservedwords.cpp`.

So there's what happens if those two files get out of sync.

Post a reply to this message

hi,

On 05/05/2016 20:22, clipka wrote:
> Thanks for your effort; unfortunately, the valgrind output is of little
> use to me without human-readable stack trace information; can you try
> again with a version of POV-Ray configured to include debug information?

yes, I ought to have thought ahead..  seeing your reply to Le_Forgeron,
I guess you have the info you needed?  otherwise, can run it (/with/
'-g' :-)) later tonight.

jr.

Post a reply to this message

Am 05.05.2016 um 22:08 schrieb jr:
> hi,
> 
> On 05/05/2016 20:22, clipka wrote:
>> Thanks for your effort; unfortunately, the valgrind output is of little
>> use to me without human-readable stack trace information; can you try
>> again with a version of POV-Ray configured to include debug information?
> 
> yes, I ought to have thought ahead..  seeing your reply to Le_Forgeron,
> I guess you have the info you needed?  otherwise, can run it (/with/
> '-g' :-)) later tonight.
> 
> jr.
> 

Everything(*) is fine now, thanks.


(* Then again, this is software development, so maybe I should rephrase
that ;))

Post a reply to this message