Re: Core dump with tip (ucom0 - external modem)
On Apr 26, To Daniel O'Connor wrote: then bt at the gdb prompt. Thanks for taking a look at it. GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd... (no debugging symbols found)... Core was generated by `tip'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libc.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.5 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)... done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x08049bd2 in connect () (gdb) bt #0 0x08049bd2 in connect () #1 0x0804d055 in send () #2 0x08049942 in sigprocmask () (gdb) I went and built tip with debugging symbols... (gdb) set args -9600 33230 (gdb) run Starting program: /usr/src/usr.bin/tip/tip/tip -9600 33230 Stale lock on ucom0 PID=6696... overriding. Program received signal SIGSEGV, Segmentation fault. 0x08049cd7 in connect () at acu.c:110 110 if (*cp != '\0') (gdb) bt 10 #0 0x08049cd7 in connect () at acu.c:110 #1 0x0804d4bd in main (argc=1, argv=0xbfbfec48) at tip.c:202 #2 0x08049a42 in _start () (gdb) checking for cp != NULL fixes the seg fault, but it still hangs for me...sigh. Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
plot.thickness++ (Re: Core dump with tip (ucom0 - external modem))
I got an interesting clue by trying ECU. Check this out: ECU is a dialer type program. I told it to use /dev/ucom0 to dial my desk phone number, and it showed itself trying to issue a bunch of commands to the modem, but each time they came back and said missed expected carriage return. It eventually gave up, but my phone then started ringing! Dialing telno 23645 on /dev/ucom0 at 9600 baud (10:24:25) Trying ecu dialer /usr/local/lib/ecu/ucom0.mi: No such file or directory modem init string not found (using default 'ATE1Q0V1') modem dial string not found (using default 'ATDT') ATE1Q0V1 missed expected carriage return got nothing ATE1Q0V1 missed expected carriage return got nothing ATE1Q0V1 missed expected carriage return got nothing ATE1Q0V1 missed expected carriage return got nothing /usr/local/lib/ecu/ucom0.mi: No such file or directory modem init string not found (using default 'ATE1Q0V1') modem dial string not found (using default 'ATDT') ATE1Q0V1 missed expected carriage return got nothing ATE1Q0V1 missed expected carriage return got nothing ATE1Q0V1 missed expected carriage return got nothing ATE1Q0V1 missed expected carriage return got nothing ATDT23645 missed expected carriage return Cannot talk to modem When it was over, I did a tip on the same device and it spewed a bunch of garbage at me: OK AT OK ATQ0V1E1 OK ATE1Q0V1 OK AT OK ATQ0V1E1 OK ATE1Q0V1 OK AT OK ATQ0V1E1 OK ATE1Q0V1 OK ATE1Q0V1 OK AT OK ATQ0V1E1 OK ATE1Q0V1 OK AT OK ATQ0V1E1 OK ATE1Q0V1 OK AT OK ATQ0V1E1 OK ATE1Q0 So all the commands were going through, but somehow being buffered...? Any knobs I can play with to help with this situation? Thanks, Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Core dump with tip (ucom0 - external modem)
Hey everybody, I am trying to set up a FBSD 5.2.1-RELEASE machine to be able to dial a number via tip as described here: http://docs.freebsd.org/doc/5.1-RELEASE/usr/share/doc/faq/serial.html (That page is a bit out of date, at least in that it says it applies to FBSD 2, 3, and 4.) My HW setup is an old pentium box with a USB to Serial cable attaching to a USR external 56k Modem. I added this to my /etc/remote tip115200|Dial any phone number at 115200 bps:\ :dv=/dev/ucom0:br#115200:at=hayes:pa=none:du: tip57600|Dial any phone number at 57600 bps:\ :dv=/dev/ucom0:br#57600:at=hayes:pa=none:du: cu115200|Use cu to dial any number at 115200bps:\ :dv=/dev/ucom0:br#57600:at=hayes:pa=none:du: tip9600|Dial any phone number at 9600 bps:\ :dv=/dev/ucom0:br#9600:at=hayes:pa=none:du: But the suggested command gives me core: tip -115200 23645 Segmentation fault (core dumped) Same result with -57600, -9600 and with cu syntax I have an entry for the usb serial device: usb1:dv=/dev/ucom0:br#9600:pa=none: And if I say tip usb1 I can issue dialer commands and it works. The ultimate goal here is having somebody be able to run a shell-script named dial-funkybox and have it dial and connect them. Sorry if I left out something important. Any thoughts? Thanks, Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Core dump with tip (ucom0 - external modem)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 27 Apr 2004 03:08, Mike Hunter wrote: tip -115200 23645 Segmentation fault (core dumped) Same result with -57600, -9600 and with cu syntax I have an entry for the usb serial device: usb1:dv=/dev/ucom0:br#9600:pa=none: And if I say tip usb1 I can issue dialer commands and it works. The ultimate goal here is having somebody be able to run a shell-script named dial-funkybox and have it dial and connect them. Sorry if I left out something important. Any thoughts? Can you generate a back trace from the coredump? gdb `which tip` tip.core then bt at the gdb prompt. BTW for this sort of thing I use expect and kermit.. - -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAjbPi5ZPcIHs/zowRAtv7AJwLc2wlgBpf/rIiTjO/biYHyM8ERwCfWwvt 1H4t3oxS6BqpR736xOtSGas= =lfjn -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Core dump with tip (ucom0 - external modem)
On Apr 27, Daniel O'Connor wrote: -BEGIN PGP SIGNED MESSAGE- On Tue, 27 Apr 2004 03:08, Mike Hunter wrote: tip -115200 23645 Segmentation fault (core dumped) Same result with -57600, -9600 and with cu syntax I have an entry for the usb serial device: usb1:dv=/dev/ucom0:br#9600:pa=none: And if I say tip usb1 I can issue dialer commands and it works. The ultimate goal here is having somebody be able to run a shell-script named dial-funkybox and have it dial and connect them. Sorry if I left out something important. Any thoughts? Can you generate a back trace from the coredump? gdb `which tip` tip.core then bt at the gdb prompt. Thanks for taking a look at it. GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd... (no debugging symbols found)... Core was generated by `tip'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libc.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.5 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)... done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x08049bd2 in connect () (gdb) bt #0 0x08049bd2 in connect () #1 0x0804d055 in send () #2 0x08049942 in sigprocmask () (gdb) Any way I can get more info for you? BTW for this sort of thing I use expect and kermit.. I started toying around with kermit when I was getting to depressed with tip...I'll give it more of a shot tomorrow. Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]