#744215 wvdial: Segmentation fault during modem initialization

Package:
wvdial
Source:
wvdial
Description:
intelligent Point-to-Point Protocol dialer
Submitter:
Daniel Bernardo
Date:
2025-02-10 14:45:03 UTC
Severity:
important
Tags:
#744215#5
Date:
2014-04-11 13:24:50 UTC
From:
To:
#744215#10
Date:
2014-04-11 14:10:23 UTC
From:
To:
root@sunblade:~# 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
--> Modem initialized.
Segmentation fault
root@sunblade:~# dmesg | tail
(.)
[878196.567143] wvdial[29961]: segfault at ff868964 ip 00000000f7726d88 (rpc
00000000f7726d6c) sp 00000000ff766350 error 30001 in
libwvbase.so.4.6[f76f0000+74000]

Curious enough while getting debug information to add to this ticket I found
out running # strace wvdial works. if you can ignore the constant output.
and when terminated closes normally.
#744215#15
Date:
2014-08-04 06:45:03 UTC
From:
To:
Dear Maintainer,
I've currently using wvdial since many year on my system and it never
ever
occurs the error reported in this bug report.

The connection on my usb GSM-modem works smoothly. The system has always
be
updated regularly. Maybe the bug is specific to the previous user
installation (like maybe the Architecture). Therefore I would suggest to
update the severity of the bug in order to let it get into the testing
reposiory.

Thank you,

Risca.



Here some additional information:
#744215#20
Date:
2014-08-06 13:56:24 UTC
From:
To:
Hello,

Thank you for this information. It seems indeed that the severity of this
bug is overinflated. I'm downgrading it to important.

Thierry, as the wvdial maintainer, it's your responsibility to handle
bug reports and to ensure that the package remains in testing. Are
you still up to the task? If not, maybe you should consider orphaning
the package.

Daniel, if you are not able to provide some more specific information
of how to reproduce it and/or a full backtrace, I doubt that this bug can
be fixed. Upstream developers likely don't have access to sparc machines.

BTW Daniel, are you still having the problem? Can you reproduce it
on another architecture?

Thank you!
#744215#29
Date:
2025-02-10 00:02:09 UTC
From:
To:
Everything was working fine in bookworm, and even in trixie at the
start. Some update (perhaps rfcomm?) may have eventually caused this
segmentation fault...
#744215#34
Date:
2025-02-10 14:41:36 UTC
From:
To:
Hi,

It seems unlikely that bug #744215 from 2014 would be the same thing
as what you are seeing in 2025. Please open a new bug and provide
all details, including a full log, backtrace and your config and so
on.

Without details this is not actionable.

Chris