[Xorp-hackers] xorp_rtrmgr : Floating point exception

[Pavlin Radoslavov]

Selçuk Cevher <cevhers at gmail.com> wrote:

> I think that it was a kind of "version mismatch" problem. I actually
> compiled XORP source code including the new process I am trying to add in
> some Linux machine, and had to try to use the compiled code in some other
> Linux machine. When I ran rtrmgr in the machine where I actually compiled
> the xorp source code, I did not get that floating point exception error.
> However, now, although rtrmgr is running, after it starts and then
> configures some of the processes in the current configuration file
> (config.boot) succesfully, it goes into a loop in which it repeatedly tries
> to validate with some XRL with the following message:
> 
> Validating with XRL: >finder://new_process_target/common/0.1/get_status<
> 
> Apparently, it can not validate it, and keeps trying.

I guess this happens while the rtrmgr is trying to start your new
process. The rtrmgr uses the get_status XRL to check the status of a
process it tries to startup, reconfigure or shutdown, and it is up
to the process to set that status properly.
For example, the status of the process must be PROC_READY before the
rtrmgr considers the process configured and running.

See libxorp/status_codes.h for detailed description of all possible
states.
Also, grep for PROC_ in the static_routes/ directory to see how
those states are used in the StaticRoutes process.

Hope that helps,
Pavlin


> Thanks.
> Selcuk
> On Thu, Apr 17, 2008 at 9:23 AM, Bruce M. Simpson <bms at icir.org> wrote:
> 
> > Selçuk Cevher wrote:
> >
> > > Below is the backtrace from gdb:
> > >  (gdb) run xorp_rtrmgr
> > > Starting program: /home/selcuk/xorp.deneme/rtrmgr/xorp_rtrmgr
> > > xorp_rtrmgr
> > > Reading symbols from shared object read from target memory...done.
> > > Loaded system supplied DSO at 0xffffe000
> > > Program received signal SIGFPE, Arithmetic exception.
> > > 0x447e61e6 in do_lookup_x () from /lib/ld-linux.so.2
> > > (gdb) bt
> > > #0  0x447e61e6 in do_lookup_x () from /lib/ld-linux.so.2
> > > #1  0x447e6569 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2
> > > #2  0x447e7d1a in _dl_relocate_object () from /lib/ld-linux.so.2
> > > #3  0x447e0833 in dl_main () from /lib/ld-linux.so.2
> > > #4  0x447f056b in _dl_sysdep_start () from /lib/ld-linux.so.2
> > > #5  0x447df48f in _dl_start () from /lib/ld-linux.so.2
> > > #6  0x447dd847 in _start () from /lib/ld-linux.so.2
> > > Thanks.
> > > Selcuk
> > >
> >
> > This looks like it is most likely a compiler or linkage problem -- the
> > process is dying in the runtime linker, before any code in the executable
> > itself has been called.
> >
> > Which compiler are you using, and on which Linux distribution?
> >
> > Posting the output of 'g++ -dumpspecs' and 'ldd xorp_rtrmgr' provides more
> > background information for errors like this.
> >
> > Thanks,  BMS
> >
> >
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers