[antlr-interest] Debug port problem in Visual Studio test project
Dennis Brothers
brothers at bros.com
Tue Apr 21 13:15:13 PDT 2009
I pretty much gave up looking for a solution. I still have the
standalone test harness, and I comment out the system dependencies if
I need to see the parse tree or AST (increasingly rarely, as the
project matures).
- Dennis Brothers
On Apr 21, 2009, at 12:07 PM, Jacob Buys wrote:
> I'm having the exact same problem. Any luck figuring out what causes
> it?
>
> On Feb 10, 11:50 pm, Dennis Brothers <broth... at bros.com> wrote:
>> I'm developing a parser to be integrated into a large system (C#
>> target). When I run it in a VS unit-test project in debug mode,
>> ANTLRWorks connects to it, and shows the beginning of the parse
>> when I
>> hit Step Forward. When I hit Step Forward again, the project throws
>> an exception "Unabletowritedatato thetransportconnection: An
>> establishedconnectionwas aborted by the software in your host
>> machine". I'm using a port (81) that is unused by anything on the
>> machine. If I switch to port 49000 (also unused), I get the same
>> behavior.
>>
>> A simpler, console-app test harness worked fine in the debugger, but
>> the full-up parser requires the context of the large project.
>>
>> I've done a lot of Googling, looking for anything about port behavior
>> in a VS test/debug environment, and come up empty. Has anyone seen
>> anything like this? I'd really like to see the ASTs my parser is
>> generating.
>>
>> - Dennis Brothers
>>
>> List:http://www.antlr.org/mailman/listinfo/antlr-interest
>> Unsubscribe:http://www.antlr.org/mailman/options/antlr-interest/your-email-address
>
More information about the antlr-interest
mailing list