On 2006/02/11 02:59, Stuart Henderson wrote:
> Attached, tested only on i386 so far.
I've been running with this on i386 for a couple of days and
some testing on sparc64, Ben's looked again and reports it's
fixed the IAX problem on sparc64 too. Any chance it could be
committed at this point? Log c
On Thu, Feb 09, 2006 at 03:24:07PM +, Stuart Henderson wrote:
> Ok the parse function is just preparing things for use elsewhere,
> so the auto variable is destroyed by the time it's needed. The place
> where it's needed is actually paying some attention to alignment
> since they memcpy, but I
On 2006/02/10 23:57, steven mestdagh wrote:
> no answer to your mail, but for those of you working on the asterisk
> port, can you also
> - make it honor CC
> - fix WANTLIB (run lib-depends-check)
thanks for the feedback steven.
Attached, tested only on i386 so far. This includes memcpy/bcopy cha
no answer to your mail, but for those of you working on the asterisk
port, can you also
- make it honor CC
- fix WANTLIB (run lib-depends-check)
thanks
steven
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
On 2006/02/08 19:16, Ben Lovett wrote:
> On Feb 7, 2006, at 11:30 AM, Jason Wright wrote:
> >Ugly code, but a simple fix might be:
>
> I don't get a SIGBUS anymore, but it still fails to register with the
> server properly.
Thanks for trying it Ben,
> >Without looking at the actual code, it's h
On Feb 7, 2006, at 11:30 AM, Jason Wright wrote:
Ugly code, but a simple fix might be:
I don't get a SIGBUS anymore, but it still fails to register with the
server properly.
--ben
Stuart Henderson <[EMAIL PROTECTED]> writes:
> Does anyone have time to help with an alignment problem in
> asterisk that was reported to me? I've been trying to learn
> enough C to work it out myself but haven't had luck/time yet
> and with 3.9 approaching thought it would be better to ask.
>
>
Does anyone have time to help with an alignment problem in
asterisk that was reported to me? I've been trying to learn
enough C to work it out myself but haven't had luck/time yet
and with 3.9 approaching thought it would be better to ask.
The offending code seems to be line 699 of channels/iax2-p
