[Asterisk-Users] Build on Itanium fails

[Jonas Arndt]

Dave,

A segmentation fault is usually caused by the program writing in a 
memory area that is not allocated (it could be a result of the optimizer 
sometime as well). That means that it can potentially overwrite code 
that are executing there. In worst case scenario you could even cause a 
kernel Oops. A software that discovers that it is missing a conf file 
will obviously have a potential of not working. However, instead of 
writing in a memory area that it has not allocated, it should inform 
about the situation in a log file

Now, if you are putting a software on the market that would take down 
your system just because you are missing or having an incorrect 
configuration file, you will find a lot of people seeing that as a bug. 
Imagine ntp segfault and coredump just because the /etc/ntp.conf is not 
there.

I think my problem is caused by the 32 versus 64 bits difference on 
Itanium. Belive me, I have seen this before.

Anybody out there with experience of compiling this animal on Itanium?

By the way, I just built it and ran it on another architecture. Without 
the conf files and there was no segmentation fault.

Thanks,

// Jonas

Anyhow, I think

Dave Cotton wrote:

>On Tue, 2005-08-09 at 13:55 -0600, Jonas Arndt wrote:
>
>  
>
>>I will do that. I think you are missing the point here though. If a
>>program would SegFault from missing conf files, it would be a HUGE
>>bug. 
>>    
>>
>
>Why is it a _huge_ bug? The software _will not_ run without it's config
>files in place. This is clearly stated in the make cycle. Must the
>programers put a check in every time to help those who want to try their
>own method? 
>
>  
>
>>The problem I am facing is most likely due to my plattform. 
>>    
>>
>
>>From reading this thread I doubt it.
>
>  
>
>>As they have build Debian packages for Itanium I was hoping that
>>somebody would have experience with compiling on Itanium and could
>>give me some pointers.
>>    
>>
>
>A maker of plastic model kits found many cases where people could not
>put the model together, they simply said "If your method doesn't succeed
>kindly read our instructions"
>
>
>  
>