Well, actually the fix might be included. Though it is not listed in the release notes as I didn't receive any confirmation from you. So can you try to reproduce it with 4.3.2?

martin wrote:

...so I can send you back a debug version of WinSCP to test?

...I never meant to ignore this post (I read it a while ago, but never replied), but as you can see, I haven't registered on this forum yet.

I was wondering, is this fix in 4.3.2 or are you waiting for me to test the debug version?

Could you possibly just link to a beta/debug version here?

I to have fixed the above problem. Can you send me an email, so I can send you back a debug version of WinSCP to test? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

Anonymous wrote:

Have you tried my "Steps to reproduce" above?

Not yet, I have it on TODO list :)

Have you tried my "Steps to reproduce" above?

Anonymous wrote:

Also, when I Abort, sometimes WinSCP will get really irritated & do "Invalid Access to Memory" or even crash/close.

martin wrote:

Can you reproduce this easily?

Anonymous wrote:

...yes, but I need to try with newer versions 1st.

...I have now tested with 4.2.8 (no not the "most recent stable" {4.2.9} or even the "current beta" {4.3.1}, but newer none-the-less).

Steps to reproduce...tested on WinSCP 4.2.8...

1. Connect to a server
   
2. Click toolbar button: "Open Terminal (Ctrl+T)"
   
3. Type any interactive command (I used "nslookup"), press Enter
   
4. Wait for "Abort" window, click Abort
   
5. Click Reconnect (or wait for timeout)
   
6. Get Error msg: "Can't end transaction, not in transaction", click OK.
   
7. "Terminal" window closes, you are returned to file list/main window
   
8. Click toolbar button: "Open Terminal (Ctrl+T)"
   
9. Type any interactive command (I used "nslookup"), press Enter
   
10. Wait for "Abort" window, click Abort
    
11. Click Reconnect (or wait for timeout)
    
12. This time, it seems to reconnect fine, however...
    
13. Type any command (interactive or not...I used "nslookup"), press Enter
    
14. Get Error msg: "Invalid access to memory", click OK.
    
15. Repeat step 13, keep getting error in step 14, stop repeating when bored.
    
16. Close Terminal window, since it seems useless/broken.
    
17. Terminal window closes, returned to main window, however...
    
18. Get Error msg: "Abnormal program termination", click OK.
    
19. All of WinSCP closes.

Bug - Forum: Why is the above list, a numbered list, not indented as far as bulleted lists?

Examples...

List with no bullets or numbers

• List with bullets

1. List with numbers

...all of those should be indented at the same level, but they aren't on this forum (they are on other phpBB forums)...or to phrase that another way: the word "List" in all of those above should line-up & the bullets or numbers should be indented some, not left aligned with normal text.

Also, on this forum only, I need to add a blank line before a list or it's "smooshed together"...

Smooshed...

...with list

1 blank line away...

...from list

...also note there is way too much space after lists, this is more apparent with nested lists...

Nested List...

• Level 1
  
  • Level 2
    
    • Level 3

...after nested list. This line is waay to far below, but looks fine on other phpBB forums. Hrm? Now I'm confused, in preview that looks fine, but I was sure this forum was doing that...was this fixed recently?

Anyway, ignoring the "Nested List" issue (that I can't reproduce right now), look at the "Examples..." above...there is a large blank line between each example, now look at the post's source, they are smooshed as close as I can get them to remove space, however the space remains.

Anonymous wrote:

...I believe when I do that, I can't even type commands, at all.

...I was a little confused. After I posted, I tested, the behavior I described, not being able to type commands at all, happens when you check "Don't start a shell or command at all" which I confused with your recommendation of "Don't allocate a pseudo-terminal"...you are right, when I use that 2nd option, I can type commands, just not interactive commands & Ctrl+C seems to not work. Neither does any of the "Special Commands" in the PuTTY system menu, like SIGINT, SIGTERM, SIGKILL...not sure what those "Special Commands" are for, but they seem useless, with TTY or not.

martin wrote:

Neither is possible.

...OK, how about this: I've been planning on writing a PHP/CGI script to do the "ps U <username>" or even "pstree <username>"...so I can list the processes for my username & click on them to kill them...would this be possible in WinSCP? A "kill window"...open a window that would list processes under your username (by running some command) & allow you to kill them? WinSCP could open "another session" to handle this. Is there a reason you only have "main session" & "secondary session"? What about unlimited (or many) "secondary" sessions?...or just "main", "secondary", "emergency"...the "emergency session" would be used to issue kill commands for un-freezing the 2nd session.

martin wrote:

Can you reproduce this easily?

...yes, but I need to try with newer versions 1st. I've only used WinSCP 3.8.2 (1st version I downloaded) & WinSCP 4.1.9...both are now old, but I will test & reproduce with those, then test again with something newer & report. Basically, just open the main session, open the 2nd session, type an interactive command, so it freezes, then Abort it & reconnect, repeat this until it crashes. Should only take 1 or 2 Aborts/Reconnects to crash 3.8.2 or 4.1.9.

martin wrote:

Is it worth trying to debug it?

...yes, of course. But hopefully in all those interim versions it could've been fixed.

martin wrote:

This request is tracked already...

...um, OK, it was the 80th bug tracked...are you planning on doing it?

Anonymous wrote:

...I believe when I do that, I can't even type commands, at all.

Maybe your shell or something cannot deal with absence of TTY. Or you actually can type commands, just that you do not see it? Have you tried entering a command blindly and pressing enter?

Since it can send text-based commands (somehow!), I figured it could send "the Ctrl+C character". Somehow, WinSCP knows to "wait for the command prompt to return" (cuz if it don't return in 15 secs you get that Abort msg)...so perhaps just make it "not wait" & lemme send another command, like kill or Ctrl+C.

Neither is possible.

but why didn't you just mention, in that topic, what you can compile with instead of just saying "No, you can't compile with this or that or that".

There's readme file in the source code package.

Can you make a topic (or Doc page) about what all in the source is dependent on BC++ builder?

Almost everything. Sorry, this is something what is not worth discussing at all.

I just wanna make absolutely sure there is not some way to regain control, other than fully Aborting.

I'm not aware of any.

Also, when I Abort, sometimes WinSCP will get really irritated & do "Invalid Access to Memory" or even crash/close.

Can you reproduce this easily? Is it worth trying to debug it?

About the logging twice thing: Can I ask for a pref (or point me to it if I missed it) to ALWAYS open the "Console session" when opening the "Main session"...I wanna open BOTH (at the beginning of the session) by typing the password once.

This request is tracked already:
https://beta.winscp.net/tracker/80

martin wrote:

Try to connect with PuTTY with