Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 109596 - Nano crash on open of attached file.
Summary: Nano crash on open of attached file.
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: SpanKY
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-17 10:58 UTC by Justin Keogh
Modified: 2005-10-17 16:05 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
This file crashes nano (crash_nano.txt,2.36 KB, text/plain)
2005-10-17 10:59 UTC, Justin Keogh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Keogh 2005-10-17 10:58:47 UTC
This malformed text file will crash nano on any computer I try it on. 
Systems tested:
Linux defgw 2.6.13-gentoo #1 SMP Fri Sep 2 02:41:46 MST 2005 i686 AMD Athlon(tm)
MP 2400+ AuthenticAMD GNU/Linux
Linux super2 2.6.11-gentoo-r6 #8 SMP Fri Sep 23 18:57:16 EDT 2005 i686 Intel(R)
Xeon(TM) CPU 3.60GHz GenuineIntel GNU/Linux
Linux super0 2.6.11-gentoo-r11 #2 SMP Sat Sep 10 20:32:52 EDT 2005 i686 Intel(R)
Xeon(TM) CPU 2.40GHz GenuineIntel GNU/Linux

Here is the error: 
*** glibc detected *** realloc(): invalid next size: 0x0822cd00 ***
                                                                   Aborted


Reproducible: Always
Steps to Reproduce:
1. nano crash_nano.txt
2. nano crashes
3. *** glibc detected *** realloc(): invalid next size: 0x0822cd00 ***
                                                                   Aborted


Actual Results:  
Had to close the shell manually.

Expected Results:  
Edit the file crash_nano.txt

Tested with and without Xorg, xterm. Same results.
I will have to upload the attachment crash_nano.txt to bugzilla.
Comment 1 Justin Keogh 2005-10-17 10:59:43 UTC
Created attachment 70862 [details]
This file crashes nano
Comment 2 SpanKY gentoo-dev 2005-10-17 16:05:54 UTC
works fine for me

you neglected to post `emerge info` like the bug report page told you to though