[omniORB] Linux make with OmnioRB4.0.7

[Rachana Ashok Gupta]

Hi,

I am using omniOrb 4.0.7 with Linux 2.4.18 and gcc 2.96. I have made some
simple changes to example dir.mk file which is included in GNUmakefile. my
cpp file name is gsm.cpp. And corba interfaces are pathGen johnny6 robot
imageAcquisition. Following is the dir.mk file like.
--------------------------------------
CXXSRCS = gsm.cpp

DIR_CPPFLAGS = $(CORBA_CPPFLAGS)

CORBA_INTERFACES = pathGen johnny6 robot imageAcquisition


MainController = $(patsubst %,$(BinPattern),MainController)

all:: $(MainController)

clean::
$(RM) $(MainController)

$(MainController): gsm.o $(CORBA_STATIC_STUB_OBJS) $(CORBA_LIB_DEPEND)
@(libs="$(CORBA_LIB_NODYN)"; $(CXXExecutable))

--------------------------------------------
when I run make. It keeps on giving me the following error -
gsm.cpp:1: *** missing operator. Stop.
I have also tried to run dos2unix command on gsm.cpp. Also tried removing
the header files one by one just to check whether any of them is creating
any problem. I know that the make file is correct because it runs fine
with the example eg1.cc. Can you please help me.
One more important thing. I had initially used gsm.cpp with omniORB3 on
windows and it used to work fine.
--
Regards,
Rachana A Gupta
2052, Engineering Building II
Centennial Campus, Dept of ECE, NCSU
Raleigh, North Carolina 27695-7911
Tel. #: [phone]
--------------------------
2504-205, Avent Ferry Road,
Raleigh, NC - 27606, USA.
Tel. #: [phone]

[Serguei Kolos]

Hi

I'm using omniORB 4.0.7 and after moving to the SLC4 Linux (2.6.9-34,
gcc345 compiler)
start getting crashes of my applications with stack traces showing that
crashes happened
somewhere in the _dl_runtime_resolve call of the ld-linux.so.2 library,
which was called from
one of the functions of the invoker.cc file. I attached two stack traces
at the end of this
message. Here is some additional information:
1. Exact line in the invoker.cc file where crash happens is always different
2. In order to reproduce this crash I have to run the application
several thousand
times, i.e. this happens rarely
3. The crash always happens at the very beginning of the application,
i.e. there are
no incoming/outgoing CORBA requests yet
4. I run my apps with valgrind which does not detect any problems, i.e.
it looks
like a race condition somewhere

Had anybody observed similar problems or may be someone has an idea of
what it might be
or how it can be investigated.

Any help is highly appreciated,
Cheers,
Serguei

STACK TRACE 1:
#0 0x003a47a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x006607f5 in raise () from /lib/tls/libc.so.6
#2 0x00662199 in abort () from /lib/tls/libc.so.6
#3 0x011e902e in TUnixSystem::Abort () from
/afs/cern.ch/sw/lcg/external/root/5.10.00e/slc4_ia32_gcc345/root/lib/libCore.so
#4 0x011e7458 in TUnixSystem::DispatchSignals ()
from
/afs/cern.ch/sw/lcg/external/root/5.10.00e/slc4_ia32_gcc345/root/lib/libCore.so
#5 0x011e53d9 in SigHandler () from
/afs/cern.ch/sw/lcg/external/root/5.10.00e/slc4_ia32_gcc345/root/lib/libCore.so
#6 0x011eb525 in sighandler () from
/afs/cern.ch/sw/lcg/external/root/5.10.00e/slc4_ia32_gcc345/root/lib/libCore.so
#7 <signal handler called>
#8 0x003ac43e in do_lookup_x () from /lib/ld-linux.so.2
#9 0x003ac842 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2
#10 0x003afc06 in fixup () from /lib/ld-linux.so.2
#11 0x003afb40 in _dl_runtime_resolve () from /lib/ld-linux.so.2
#12 0x0099fe14 in omniAsyncWorkerInfo (this=0xb7f88400,
worker=0x9962f40) at invoker.cc:100
#13 0x0099fdde in omniAsyncWorker::run (this=0x9962f40) at invoker.cc:139
#14 0x0088f00c in omni_thread_wrapper (ptr=0x9962f40) at posix.cc:451
#15 0x00362371 in start_thread () from /lib/tls/libpthread.so.0
#16 0x007009be in clone () from /lib/tls/libc.so.6

STACK TRACE 2:
#0 0x003a47a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x00a0a7f5 in raise () from /lib/tls/libc.so.6
#2 0x00a0c199 in abort () from /lib/tls/libc.so.6
#3 0x0118302e in TUnixSystem::Abort () from
/afs/cern.ch/sw/lcg/external/root/5.10.00e/slc4_ia32_gcc345/root/lib/libCore.so
#4 0x01181458 in TUnixSystem::DispatchSignals ()
from
/afs/cern.ch/sw/lcg/external/root/5.10.00e/slc4_ia32_gcc345/root/lib/libCore.so
#5 0x0117f3d9 in SigHandler () from
/afs/cern.ch/sw/lcg/external/root/5.10.00e/slc4_ia32_gcc345/root/lib/libCore.so
#6 0x01185525 in sighandler () from
/afs/cern.ch/sw/lcg/external/root/5.10.00e/slc4_ia32_gcc345/root/lib/libCore.so
#7 <signal handler called>
#8 0x003ac43e in do_lookup_x () from /lib/ld-linux.so.2
#9 0x003ac842 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2
#10 0x003afc06 in fixup () from /lib/ld-linux.so.2
#11 0x003afb40 in _dl_runtime_resolve () from /lib/ld-linux.so.2
#12 0x005c1ded in omniAsyncWorker::run (this=0x9fecf40) at invoker.cc:140
#13 0x0021d00c in omni_thread_wrapper (ptr=0x9fecf40) at posix.cc:451
#14 0x003c0371 in start_thread () from /lib/tls/libpthread.so.0
#15 0x00aaa9be in clone () from /lib/tls/libc.so.6

[Duncan Grisby]

Post by Rachana Ashok Gupta
I am using omniOrb 4.0.7 with Linux 2.4.18 and gcc 2.96. I have made some
simple changes to example dir.mk file which is included in GNUmakefile. my
cpp file name is gsm.cpp. And corba interfaces are pathGen johnny6 robot
imageAcquisition. Following is the dir.mk file like.

[...]

Post by Rachana Ashok Gupta
when I run make. It keeps on giving me the following error -
gsm.cpp:1: *** missing operator. Stop.

Is that the only output you get from make? If not, what else happens
beforehand?

make can be very fussy about weird characters in makefiles. Maybe you
should try rewriting the file from scratch, or copying the original
dir.mk from the examples.

Cheers,

Duncan.