LCDproc development and user support list

Text archives Help


[Lcdproc] lcdproc v0.5.3 - ConnectionType=ftdi [[ Segmentation fault ]]


Chronological Thread 
  • From: bsdfan at nurfuerspam.de (Markus Dolze)
  • Subject: [Lcdproc] lcdproc v0.5.3 - ConnectionType=ftdi [[ Segmentation fault ]]
  • Date: Sat, 23 Oct 2010 14:31:01 +0200

Hello Santanu,

please note that the hd44780 FTDI connection type is for use with FT2232 or
FT245 FIFO chips and requires special wiring. Unless you know that your MPlay
device makes use of these, the hd44780 ftdi connection is probably not what
you are looking for.

You may try hd44780's 'mplay' connection type instead.

See http://lcdproc.sourceforge.net/docs/lcdproc-0-5-3-user.html#drivers for
more information.

Regards
Markus

-------- Original-Nachricht --------
> Datum: Fri, 22 Oct 2010 10:23:15 +0100
> Von: Santanu Das <santanu at hep.phy.cam.ac.uk>
> An: lcdproc at lists.omnipotent.net
> Betreff: Re: [Lcdproc] lcdproc v0.5.3 - ConnectionType=ftdi [[
> Segmentation fault ]]

> Okay, I have the backtrace now:
>
> root at htpc:/usr/local/etc# gdb LCDd
> GNU gdb (GDB) 7.1-ubuntu
> Copyright (C) 2010 Free Software Foundation, Inc.
>
> [ .... ]
>
> Reading symbols from /usr/local/sbin/LCDd...(no debugging symbols
> found)...done.
> (gdb) run
> Starting program: /usr/local/sbin/LCDd
> LCDd version 0.5.3 starting
> Built on Oct 22 2010, protocol version 0.3, API version 0.5
> Using Configuration File: /usr/local/etc/LCDd.conf
> Set report level to 5, output to stderr
> LCDd 0.5.3, LCDproc Protocol 0.3
> Part of the LCDproc suite
> Copyright (C) 1998-2009 William Ferrell, Scott Scriven
> and many other contributors
>
> [ ... ]
>
> Server running in foreground
> Listening for queries on 127.0.0.1:13666
> screenlist_init()
> driver_load(name="hd44780",
> filename="/usr/local/lib/lcdproc/hd44780.so")
> HD44780: using ConnectionType: ftdi
> HD44780: Matrix key 3 0: "Enter"
> HD44780: Matrix key 3 1: "Up"
> HD44780: Matrix key 3 2: "Down"
> HD44780: Matrix key 3 3: "Escape"
> hd44780: Using hd44780_default charmap
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff743e5a7 in usb_control_msg () from /lib/libusb-0.1.so.4
> (gdb) bt
> #0 0x00007ffff743e5a7 in usb_control_msg () from /lib/libusb-0.1.so.4
> #1 0x00007ffff72367bf in ftdi_enable_bitbang () from
> /usr/lib/libftdi.so.1
> #2 0x00007ffff764f08c in hd_init_ftdi () from
> /usr/local/lib/lcdproc/hd44780.so
> #3 0x00007ffff764a6f3 in HD44780_init () from
> /usr/local/lib/lcdproc/hd44780.so
> #4 0x0000000000411957 in driver_load ()
> #5 0x0000000000410bd1 in drivers_load_driver ()
> #6 0x00000000004084ee in main ()
>
>
> Something went wrong during the compilation? Thanks in advance.
>
> Cheers,
> Santanu
>
> > On 22/10/2010 08:08, Thomas Jarosch wrote:
> >> On Thursday, 21. October 2010 20:59:41 Santanu Das wrote:
> >>> 4275.263767] LCDd[1537]: segfault at 0 ip 00007f49ac5aa5a7 sp
> >>> 00007fff4fc1f4d0 error 4 in libusb-0.1.so.4.4.4[7f49ac5a7000+7000]
> >>>
> >>> does it help debugging at all? Can anyone please help?
> >> Do you get a core dump or would you be able to
> >> run it inside gdb and get a backtrace?
> >>
> >> That would help the most.
> >>
> >> Cheers,
> >> Thomas
> >> _______________________________________________
> >> LCDproc mailing list
> >> LCDproc at lists.omnipotent.net
> >> http://lists.omnipotent.net/mailman/listinfo/lcdproc
> >
> > _______________________________________________
> > LCDproc mailing list
> > LCDproc at lists.omnipotent.net
> > http://lists.omnipotent.net/mailman/listinfo/lcdproc
>




Archive powered by MHonArc 2.6.18.

Top of page