From: Grigorenko D. <pos...@na...> - 2004-07-08 19:43:47
|
Hello. > This 77-th line of iostream looks like a bug in debugger or compiler > (invalid debugging information), I remember that I had similar problems > somewhere else. Your are right. I found that problem is in the lt_dlinit() call (the first call of the ltdl function). You can find it in the InitDynamicLoader() function in driver2.cc. I checked that sigfault heppens befor the first line of lt_dlinit and befor the first line of the main function in ltdl. (We have to add an empty main funcion in ltdl.c). I investigated that in case of static linking occ which ltdl.o (instead of using -lltdl) it is all right! So I think that problem is in the linking process. Namely, I think what the lt_dlinit() function address is incorrect. > From your description it is difficult to tell where the sigfault really > happens. As far as I understand line 75 is the first line of main(). > Perhaps the segfault happens during initialization of static variables. > One way to find out would be to load core file to gdb ('gdb occ core') > and examine stack trace ('bt'). It does not work on cygwin stackdump file in this way. Error: "occ.exe.stackdump" is not a core dump: File format not recognized |