> I am using ares-1.1.1 integrated in my sip application. Which is
> working well so far :)
>
> I am having this rare (non-reproduceable) system craches dues to some
> memory corruption issue in some still unidentified scenario.
>
> mention below is the backtrace of the core
>
> (gdb) bt
> #0 0x00000000 in ?? ()
> #1 0x400ca732 in time () from /lib/tls/libc.so.6
> #2 0x0830f508 in ares_process (channel=0xb50515c8, read_fds=0xb53409e0,
> write_fds=0xb5340960) at ares_process.c:57
> #3 0x082fa424 in aresReceiveDNSResponse (arg=0x0) at ../aresapi.c:346
> #4 0x00000000 in ?? ()
>
>
> Is this some known issue that has been already fixed ?? The channel
> structure is fine is all aspects.
>
> Any help on this one will be highly appreciated.
>
> awaiting eagerly for some responce to address this issue.
I doubt this is an issue with c-ares. Most likely you have a buffer
overflow in your code somewhere which causes this crash later on down
the line. Run it through valgrind, see what it says. It would be
able to catch the bad code.
-Brad
Received on 2007-08-17