bugGNU Screen - Bugs: bug #25291, Screen crashes after passing...

 
 

bug #25291: Screen crashes after passing through a zmodem transfer

Submitter:  None
Submitted:  Sat 10 Jan 2009 09:33:52 PM UTC
   
 
Category:  Crash/Freeze/Infloop Severity:  3 - Normal
Priority:  * 3 - Low Status:  Need Investigation
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release:  4.0.3
Fixed Release:  None Planned Release:  Later
Work Required:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 02 Feb 2009 08:46:21 PM UTC, comment #3: 

The backtrace, from screen 4.0.3:

(gdb) bt
#0  0x00049b54 in zmodem_parse (p=0xbc270,
    bp=0xffbfd910 "OO\030B0800000000022d\r\212\021W\030@\030@\030@\030@\030@\030@\030@¤\030@\030@\030B\030W\030@\030@\030LÌ\030@\030@\030@¼\030@\030@\030K\030W\030@\030@\030@\030@\030@\030@\030@À\030@\030@\030B\030W\030@\030@\030N\030Ü\030@\030@\030@Ø\030@\030@\030K\030W\030@\030@\030@\030@\030@\030@\030@Ü\030@\030@\030B\030W\030@\030@\030R\\\030@\030@\030@ô\030@\030@\030K\030W\030@\030@\030@\030@\030@\030@\030@ø\030@\030@\030B\030W\030@\030@\030V\030X\030@\030@\030A\030P\030@\030"..., len=2) at window.c:2042
#1  0x00048dd8 in win_readev_fn (ev=0xbc2c0, data=0xbc270 "") at window.c:1842
#2  0x000895b8 in sched () at sched.c:232
#3  0x00019a0c in main ()

If you want you can find the core+binary (compiled with -g) at
http://eischnee.de/screen-zmodem-crash.tgz
SPARC Solaris 10.



Arne Jansen <sensille>
Mon 26 Jan 2009 09:39:55 PM UTC, comment #2: 

Can you please post a backtrace from the original crash? The display store/restore might need to happen somewhere else etc. The backtrace might give a better understand of the issue.

Sadrul Habib Chowdhury <sadrul>
Group administrator
Thu 15 Jan 2009 10:49:56 PM UTC, comment #1: 

My opportunities to debug something like this are pretty small... would love a ready-made patch :D

Micah Cowan <micahcowan>
Sat 10 Jan 2009 09:33:52 PM UTC, original submission:  

I tried to use screen in zmodem pass mode. The sender was inside the screen using lsz.
The first problem is that screen didn't detect the end of the transfer. It seems lsz doesn't send the final 'OO' for some reason. So after the transfer I give a manual 'OO' which the screen detects.
This is the moment screen crashes. My debugging shows that when calling zmodem_abort(p,0) the (global) display variable is NULL.
I haven't been able to find out why this is the case, but as a test I saved the current display in zmodem_found and restored it before calling zmodem_abort and the crash was gone.
The only thing that was missing then was the status bar. It only reappeared a minute later with an update of the clock.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by sensille (Posted a comment)
  • -email is unavailable- added by sadrul (Posted a comment)
  • -email is unavailable- added by micahcowan (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-01-15 micahcowan Priority5 - Normal 3 - Low
        StatusNone Need Investigation
        PrivacyNone Public
        Planned ReleaseNone Later

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code