Hello,
Lukas Gebauer írta:
> Is time for releasing of SynaSer too. :-)
>
> So, support for non-LIBC unix based targets in Freepascal is published in
> SynaSer package. (It exists in Synasnaps before only...)
>
First of all, thanks for synaser :-) After a long delay I'm working with
it again, and ran into a problem immediately. I guess, this is a Linux
kernel problem. My applications worked on openSUSE 10.2 without any
problems (kernel 2.6.16). Now I resumed development on openSUSE 10.3,
which has a 2.6.22 kernel.
Using the same binary (from last summer) or recompiling my code with
this latest release I get the same results on 10.3:
[EMAIL PROTECTED]:~/pas/ubi_poc3> ./puborka
TGtkWSCustomMemo.CreateHandle
TApplication.HandleException Communication error 14: Bad address
Stack trace:
$08215469 TBLOCKSERIAL__EXCEPTCHECK, line 2078 of synaser.pas
$08214E31 TBLOCKSERIAL__MODEMSTATUS, line 1935 of synaser.pas
$082149FA TBLOCKSERIAL__SETRTSF, line 1683 of synaser.pas
$08212A92 TBLOCKSERIAL__CLOSESOCKET, line 763 of synaser.pas
$082129FC TBLOCKSERIAL__DESTROY, line 749 of synaser.pas
$0805F832
$0807A887 TFUBORKA__TIADAGIDOTIMER, line 92 of uborka.pas
$0817FB05 TCUSTOMTIMER__DOONTIMER, line 177 of customtimer.pas
$0817FA6F TCUSTOMTIMER__TIMER, line 152 of customtimer.pas
$081D3EC4 GTKTIMERCB, line 2918 of gtkcallback.inc
$B7F47313
$B7F4796D
$B7F481CF
$B7D34116
$0819873A TGTKWIDGETSET__APPWAITMESSAGE, line 1430 of gtk1object.inc
$0807603C TAPPLICATION__IDLE, line 312 of ./include/application.inc
$0807747F TAPPLICATION__HANDLEMESSAGE, line 944 of
./include/application.inc
[EMAIL PROTECTED]:~/pas/ubi_poc3>
And the output from strace:
open("/dev/ttyUSB0", O_RDWR|O_SYNC|O_LARGEFILE) = 8
ioctl(8, TIOCMGET, [0]) = -1 EFAULT (Bad address)
ioctl(8, TCFLSH, 0x2) = 0
ioctl(8, TIOCMGET, [0]) = -1 EFAULT (Bad address)
write(1, "TApplication.HandleException Communication error 14: Bad
address\n", 65) = 65
write(1, " Stack trace:\n", 15) = 15
Using " ser.RaiseExcept:=false; " is a workaround, and my application
works, but obviously this is not a solution, just an ugly hack :-( Could
you take a look at it?
I use the following device for serial communication (an USB->Serial chip):
usb 5-1: new full speed USB device using uhci_hcd and address 5
usb 5-1: new device found, idVendor=0403, idProduct=6001
usb 5-1: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 5-1: Product: FT232R USB UART
usb 5-1: Manufacturer: FTDI
usb 5-1: SerialNumber: A30008dk
usb 5-1: configuration #1 chosen from 1 choice
ftdi_sio 5-1:1.0: FTDI USB Serial Device converter detected
drivers/usb/serial/ftdi_sio.c: Detected FT232RL
usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB0
I use now the latest fpc and lazarus releases.
Thanks, bye,
CzP
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public
