Strange core dump in malloc() when statically linked for python development

[migs paraz]

I am now linking in my python module which I'm
finishing up.
 
To make testing easier, I linked in all modules
statically.
 
When the python module is included, I get a SIGSEGV
and the following backtrace:
 
#0  ptmalloc_init () at malloc.c:1713
#1  0x4026de64 in malloc_hook_ini (sz=21,
caller=0x40270a34) at malloc.c:1856
#2  0x40269f8d in __libc_malloc (bytes=21) at
malloc.c:2798
#3  0x40270a34 in __strdup (s=0x810ab28
"/usr/local/etc/raddb") at strdup.c:43
#4  0x08058b23 in main (argc=4, argv=0xbffff9fc) at
radiusd.c:550
#5  0x40206507 in __libc_start_main (main=0x8058a9c
<main>, argc=4, 
    ubp_av=0xbffff9fc, init=0x8056d20 <_init>,
fini=0x81098e0 <_fini>, 
    rtld_fini=0x4000dc14 <_dl_fini>,
stack_end=0xbffff9ec)
    at ../sysdeps/generic/libc-start.c:129
 
Where radiusd.c:550 is:

  radius_dir = strdup(RADIUS_DIR);

 
 
It seems that linking in the Python interpreter or
something else linked for my the module caused this
memory allocation problem.

Thanks!


=====
Miguel A.L. Paraz

Discussion for all Working Filipinos:
http://groups.yahoo.com/group/theworkingfilipino

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/