Bug 525722 - minicom crash
Summary: minicom crash
Keywords:
Status: CLOSED DUPLICATE of bug 555283
Alias: None
Product: Fedora
Classification: Fedora
Component: minicom
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-25 12:09 UTC by Sergei LITVINENKO
Modified: 2010-03-09 13:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-09 13:16:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
strace log where minicom is crashed (3.88 KB, application/x-bzip2)
2009-09-25 12:09 UTC, Sergei LITVINENKO
no flags Details

Description Sergei LITVINENKO 2009-09-25 12:09:03 UTC
Created attachment 362664 [details]
strace log where minicom is crashed

Description of problem:
If system locale is ru_RU.UTF-8, as soon as minicom try to init modem it crash
with message in backtrace *** buffer overflow detected ***:


Version-Release number of selected component (if applicable):
minicom-2.3-6.fc12.i686

How reproducible:
100%

Steps to Reproduce:
1. Use locale ru_RU.UTF-8
1. Connect mobile phone by USB
2. Setup minicom to use /dev/ttyACM0: minicom -s (serial port setup)
3. Save setting as dfl
4. Run minicom
  
Actual results:
Minicom crash with backtrace log

Expected results:
Minicom work

Additional info:
1. `export LC_ALL=C ; export LANG=C; minicom` help.
2. If I understand good, some russian messages to overflow buffer

Comment 1 Bug Zapper 2009-11-16 12:56:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Stas Sergeev 2010-01-14 09:59:16 UTC
Please try the fix in Bug 555283.

Comment 3 Jan Görig 2010-03-09 13:16:47 UTC

*** This bug has been marked as a duplicate of bug 555283 ***


Note You need to log in before you can comment on or make changes to this bug.