[Asterisk-Dev] I hate when this happens

[David Pollak]

Brian,

Thanks for confirming that you've seen the same thing.  I'm beginning to 
think that something is stomping on the PostgreSQL ODBC's memory space.  
Nothing have changed in the ODBC parts of the call stack, yet there are 
problems when the PostgreSQL ODBC drivers with newer versions.  I've got 
some other stuff I need to work on before I need to get to the latest 
version of * (I need the ChanSpy stuff, but not just yet.)  I'll wait a 
couple of weeks.  If the CVS head version is still PostgreSQL unfriendly 
at that time, I'll do digging to see what's tromping on the ODBC driver.

Thanks,

David

Brian Capouch wrote:

> David Pollak wrote:
>
>> Jared,
>>
>> This doesn't seem to have fixed the issue.  It seems that 
>> multi-parameter queries sent to PostgreSQL cause the seg fault.  Is 
>> anyone else out there using PostgreSQL?
>>
>
> I am, but only with a native-Postgres res_config driver that I hacked 
> from the MySQL driver that Matt hacked from the ODBC driver that I 
> think Mark wrote.
>
> It works perfectly for me, except with recent CVS-HEAD (after the 
> jitterbuffer was put in).  All versions since then are unusable for me 
> on either platform I run.
>
> I don't know your environment.  If it's recent CVS-HEAD, you might 
> revert to something from ca 3/18 and see if that fixes it.
>
> The behavior of recent HEAD versions on my WRT54s (MIPSEL processor) 
> is immediate crashes when calls come in, without a core dump.  On x86 
> it is a gradual degradation of processing calls that always results in 
> a hung server, anywhere from 1-12 hours after it is started.
>
> FWIW.
>
> B.
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev