From: tuxslack <tuxslack@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] wvdial - segmentation fault
Date: Thu, 13 Jun 2024 06:05:03 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50811@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4779 bytes --]
New issue by tuxslack on void-packages repository
https://github.com/void-linux/void-packages/issues/50811
Description:
### Is this a new report?
Yes
### System Info
Void Linux kernel 6.6.32_1 x86_64
### Package(s) Affected
wvdial-1.61_8 x86_64
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Use wvdial without Segmentation Fault.
### Actual behaviour
wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1 S2 S3
ttyUSB0<*1>: ATQ0 V1 E1 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB0<*1>: Modem Identifier: ATI -- Manufacturer:
ttyUSB0<*1>: Speed 9600: AT -- OK
ttyUSB0<*1>: Max speed is 9600; that should be safe.
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 -- ^BOOT:23425710,0,0,0,88
ttyUSB1<*1>: failed with 2400 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB1<*1>: Modem Identifier: ATI -- Manufacturer:
ttyUSB1<*1>: Max speed is 9600; that should be safe.
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttyUSB0.
Modem configuration written to /etc/wvdial.conf.
ttyUSB0<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
ttyUSB1<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
wvdial
--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP",""
AT+CGDCONT=1,"IP",""
OK
--> Modem initialized.
--> Sending: ATDT
--> Waiting for carrier.
ATDT*99#
CONNECT
--> Carrier detected. Waiting for prompt.
Falha de segmentação
ldd `which wvdial`
linux-vdso.so.1 (0x00007fff5fbf0000)
libuniconf.so.4.6 => /usr/lib/libuniconf.so.4.6 (0x00007ff94f211000)
libwvstreams.so.4.6 => /usr/lib/libwvstreams.so.4.6 (0x00007ff94f140000)
libwvutils.so.4.6 => /usr/lib/libwvutils.so.4.6 (0x00007ff94f017000)
libwvbase.so.4.6 => /usr/lib/libwvbase.so.4.6 (0x00007ff94ef86000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007ff94ec00000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007ff94ef62000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007ff94ea16000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007ff94ef46000)
libssl.so.3 => /usr/lib/libssl.so.3 (0x00007ff94e920000)
libcrypto.so.3 => /usr/lib/libcrypto.so.3 (0x00007ff94e200000)
libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x00007ff94ef0a000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007ff94f2ae000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007ff94e83e000)
xbps-query -S wvdial
architecture: x86_64
conf_files:
/etc/ppp/peers/wvdial
/etc/ppp/peers/wvdial-pipe
filename-sha256: 670b6d9d516430fb74d03f51b717291de7814322d0ee90685947f8140c0cf5c9
filename-size: 72KB
homepage: https://code.google.com/p/wvstreams/
install-date: 2024-01-18 02:06 -03
installed_size: 190KB
license: LGPL-2.0-only
maintainer: Enno Boland <gottox@voidlinux.org>
metafile-sha256: fdad885aab176434c6c006d56f8ca1316c6fb88cbf1a538a7a197e99e167bf3a
pkgname: wvdial
pkgver: wvdial-1.61_8
repository: https://repo-default.voidlinux.org/current
run_depends:
ppp>=0
wvstreams>=4.6.1_20
libstdc++>=4.4.0_1
libgcc>=4.4.0_1
glibc>=2.32_1
shlib-requires:
libuniconf.so.4.6
libwvstreams.so.4.6
libwvutils.so.4.6
libwvbase.so.4.6
libstdc++.so.6
libgcc_s.so.1
libc.so.6
short_desc: Point-to-Point Protocol dialer
source-revisions: wvdial:afca7b0266
state: installed
### Steps to reproduce
To reproduce the bug just run wvdial as Root which at the end of the output shows "Segmentation fault".
The /etc/wvdial.conf file is configured.
wvdial
--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP",""
AT+CGDCONT=1,"IP",""
OK
--> Modem initialized.
--> Sending: ATDT
--> Waiting for carrier.
ATDT
CONNECT
--> Carrier detected. Waiting for prompt.
**Segmentation fault**
next reply other threads:[~2024-06-13 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 4:05 tuxslack [this message]
2024-06-14 10:02 ` sgn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50811@inbox.vuxu.org \
--to=tuxslack@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).