[Radiance-general] rtrace seg fault

Martin Moeck MMoeck at engr.psu.edu
Fri Mar 24 15:42:36 CET 2006


Actually, I had the same problem with rtcontrib. It can easily be invoked by setting -ad higher than 26000.
 
Martin Moeck, Penn state

________________________________

From: radiance-general-bounces at radiance-online.org on behalf of J. David Maino
Sent: Fri 3/24/2006 9:31 AM
To: Radiance general discussion
Subject: Re: [Radiance-general] rtrace seg fault



Greg,

After upgrading to the latest HEAD release I've been running several
different runs over the past day and it seems that the seg fault is
gone, but now there is another message that I am getting:

*** glibc detected *** realloc(): invalid next size: 0x08060248
Aborted
rtrace: signal - Broken pipe

It seems to work OK when I split my sensor input file up into smaller
segments (of 100-200 calculation points) but when I try the whole file
(around 2000 points) is when it has problems now. I'm running the latest
HEAD release on Ubuntu Linux (Breezy Badger) just for reference. For
now, I'm fine with using the "split" command as a workaround and
calculating the contributions in segments, but I was wondering if there
is again perhaps something that I'm doing wrong?

Thanks,

Dave

Gregory J. Ward wrote:
> Hi Dave,
>
> It sounds like rtcontrib is bombing, not rtrace.  Are you on the
> latest HEAD release?  We had some problems with the official release
> of rtcontrib under Linux, I know.  I don't remember any seg faults,
> but the Cygwin binaries seem to be prone to those if you're under Cygwin.
>
> -Greg
>
>> From: "J. David Maino" <maino at psu.edu>
>> Date: March 22, 2006 10:09:13 AM PST
>>
>> Hello all,
>>
>> rtrace has been  giving me some trouble lately, but it doesn't seem
>> to be consistent. I get the following error from time to time:
>>
>> rtrace: signal - Broken pipe
>> Segmentation Fault
>>
>> It usually happens while running rtcontrib, but not always. Sometimes
>> it will run fine with no problems, but then the same geometry with
>> the same command produces and error and it is not always at the same
>> point. Sometimes it is right away, sometimes a few minutes into it,
>> and sometimes a few hours into it. Is this more a memory/hardware
>> issue, or could it be a problem with the way I arrange my files? Any
>> help you could offer would be greatly appreciated.
>>
>> Thanks,
>>
>> Dave
>
> _______________________________________________
> Radiance-general mailing list
> Radiance-general at radiance-online.org
> http://www.radiance-online.org/mailman/listinfo/radiance-general
>
>

_______________________________________________
Radiance-general mailing list
Radiance-general at radiance-online.org
http://www.radiance-online.org/mailman/listinfo/radiance-general


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 6012 bytes
Desc: not available
Url : http://radiance-online.org/pipermail/radiance-general/attachments/20060324/5426a23c/attachment.bin


More information about the Radiance-general mailing list