LCDproc development and user support list

Text archives Help

[Lcdproc] OpenBSD glcd (Cannot load specified object)

Chronological Thread 
  • From: harald at (Harald Geyer)
  • Subject: [Lcdproc] OpenBSD glcd (Cannot load specified object)
  • Date: Mon, 22 Feb 2016 17:34:27 +0100

Brendan Horan writes:
> Sorry for the top post. Digging at this a little more.. Running with the
> following syntax "LD_DEBUG=1 server/LCDd -r5 -f -c LCDd.conf"
> I see the following error! :
> ----------------------------------------------------------------------
> loading: required by
> /usr/local/lib/ flags /usr/lib/
> = 0x68 dlopen: failed to open
> ----------------------------------------------------------------------
> AHA! but the file is shared object is present :
> ----------------------------------------------------------------------
> # file /usr/lib/ /usr/lib/
> ELF 64-bit LSB shared object, x86-64, version 1
> ----------------------------------------------------------------------

Yes, according to the ktrace you provided, dlopen reads libpthread
successfully and whatever goes wrong is not visible at the syscall level ...

> Lets try a preload...
> ----------------------------------------------------------------------
> # LD_PRELOAD=/usr/lib/ server/LCDd -r5 -f -c LCDd.conf
> <SNIP> Server running in foreground Listening for queries on
> screenlist_init() driver_load(name="glcd",
> filename="server/drivers/") glcd_init() glcd: using
> ConnectionType: glcd2usb glcd/glcd2usb: no GLCD2USB device found Driver
> [glcd] init failed, return code -1 Module server/drivers/
> could not be loaded Could not load driver glcd There is no
> output driver Critical error while initializing, abort.
> ----------------------------------------------------------------------


> That looks a lot better! I will re-attach the LCD to the machine
> later today. I will then test again. I am unsure of the correct way
> to fix this. I assume the linker section or Makefile details for the
> "drivers" section needs to be edited somehow to force it to include the
> "" ?

dlopen() is a nightmare - every libc implements it a bit differently and
everything except for the most basic use cases is not working portably.

At this point the only approach I can think of is
* get debugging symbols for your libc
* step with the debugger through dlopen() to see where it fails

However that's only the easy part. The hard part probably will be
figuring out who is wrong and where to report the bug. :(

Sorry I can't be of more help.

If you want to support my work:
or donate via peercoin to P98LRdhit3gZbHDBe7ta5jtXrMJUms4p7w
or bitcoin 1FUtd8T9jRN1rFz63vZz7s2fDtB6d6A7aS

Archive powered by MHonArc 2.6.18.

Top of page