Am 20.01.2014 um 05:47 schrieb Sebastian Kuzminsky <s...@highlab.com>:
> On 01/19/2014 06:47 PM, Michael Haberler wrote: >> >> reading back on IRC: >> >>> [17:20:41] <seb_kuzminsky> zultron: i'm trying to debug that hal_init >>> problem i'm seeing in packaged ubc, and i'm confused as to why the >>> rtapi_print_msg() calls in hal_init_mode() aren't showing up in the logs >> >> This is because it's a chicken-and-egg problem - RTAPI logging needs a >> shared memory segment for log messages; if the ULAPI-side RTAPI init fails, >> this is not possible, which is why error messages go to stderr until that >> init step succeeds. > > The rtapi_print_msg() calls in ulapi_load() don't show up in either the > syslog or on stderr, any idea why that is? try running with ULAPI_DEBUG=5 halcmd this should trace the actions in ulapi_load() - it's necessary for the same shm reason (the global debug levels are not accessible yet) re cradek/rpath: this is no different in ub, but it might be an rpath path is off in the build or lost in the non-RIP build Seb: can you see what chrpath -l says? this should give a clue: $ chrpath -l bin/halcmd bin/halcmd: RPATH=/bighome/mah/emc2-rtos/lib -Michael ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
