[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
RE: Tor 0.1.1.6-alpha is out
- To: <or-talk@xxxxxxxxxxxxx>
- Subject: RE: Tor 0.1.1.6-alpha is out
- From: "Edman, Matt" <Matt_Edman@xxxxxxxxxx>
- Date: Mon, 12 Sep 2005 15:23:01 -0500
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Mon, 12 Sep 2005 16:23:20 -0400
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- Thread-index: AcW3s+QsOJxevWB7QxmN0GQ6hNfw1gAI3v1w
- Thread-topic: Tor 0.1.1.6-alpha is out
More specifically, Tor is crashing trying to return from
connection_edge.c:connection_edge_end().
I believe this is caused by a change to connection_edge_end() in
http://archives.seul.org/or/cvs/Sep-2005/msg00003.html
This patch to 0.1.1.6-alpha should fix it:
--- connection_edge.c.orig 2005-09-12 16:17:28.000000000 -0400
+++ connection_edge.c 2005-09-12 16:17:44.000000000 -0400
@@ -173,7 +173,7 @@
int
connection_edge_end(connection_t *conn, char reason, crypt_path_t
*cpath_layer)
{
- char payload[5];
+ char payload[9];
size_t payload_len=1;
circuit_t *circ;
-----Original Message-----
From: owner-or-talk@xxxxxxxxxxxxx [mailto:owner-or-talk@xxxxxxxxxxxxx]
On Behalf Of alien
Sent: Monday, September 12, 2005 12:06 PM
To: Bob
Subject: Re: Tor 0.1.1.6-alpha is out
Hi Bob,
Saturday, September 10, 2005, 3:08:46 PM, you wrote:
> I installed this last night, and I'm getting stack corruption errors
> around "Payload"?
The complete error message is:
===================================
Microsoft Visual C++ Debug Library
Debug Error!
Program: C:\Program Files\Tor\tor.exe
Module: C:\Program Files\Tor\tor.exe
File:
Run-Time Check Failure #2 - Stack around the variable 'payload' was
corrupted.
Press retry to debug the application
===================================
"Retry" will crash Tor.
I'm getting it too after installing the new tor-0.1.1.6-alpha-win32. I
reverted back to tor-0.1.1.5-alpha-win32 and started getting with it as
well! Now that's odd, I didn't have this before...
It doesn't happen immediately, maybe an hour after starting.
--
cheers!
alien mailto:alien51@xxxxxxxxxxxx
.. Success always occurs in private, and failure in full view.