I have had a tiny bit more success now. I had to fill in the tdmlConfig
parts of the launch.json:

"tdmlConfig": {
"action": "none",
"name": "tdml1",
"description": "tdml1",
"path": "${workspaceFolder}/target/foo.tdml"
}

Now I get to the first stop on the schema root.



On Fri, Apr 28, 2023 at 12:23 PM Mike Beckerle <[email protected]> wrote:

> Operating system is Ubuntu 20.04.
>
> I have changed that to 4712, and that also fails same way.
>
>
> On Fri, Apr 28, 2023 at 12:11 PM Davin Shearer <[email protected]> wrote:
>
>> Hi Mike,
>>
>> So it appears that the daffodil debugger server is not able to start and
>> listen on TCP port 4711 given the error message in your email.  The
>> daffodil debugger server is different from the server that is used by the
>> data editor that comes up by default on port 9000 that you've configured
>> now to use 9001.  What operating system are you using?  /bin/bash suggests
>> non-WIndows.
>>
>>
>> On Fri, Apr 28, 2023 at 11:43 AM Mike Beckerle <[email protected]>
>> wrote:
>>
>> > No luck yet in getting this off the ground. I am unable to get this to
>> even
>> > start and hit the first stop point at the root schema element.
>> >
>> > My example is PCAP, from the github DFDL schemas site, which uses
>> > ethernetIP, also from that site.
>> >
>> > I changed the data editor port to 9001.
>> >
>> > I still get: The terminal process "/bin/bash '--login', '-c',
>> > './daffodil-debugger --listenPort 4711'" terminated with exit code: 1.
>> >
>> >
>> > On Tue, Apr 25, 2023 at 10:49 PM Shane Dell <[email protected]>
>> wrote:
>> >
>> > > What Davin posted would make the most sense. Based on your output it
>> > would
>> > > seem that you
>> > > are running something on port 9000 already. Inside of you
>> > > .vscode/launch.json if you add this:
>> > >
>> > > "dataEditor.omegaEditPort": 9001
>> > >
>> > > to your configuration, the data editor should now try to run on port
>> > 9001.
>> > > FYI, You don't have to
>> > > make it 9001 it can be whatever open port you would like.
>> > >
>> > > Thank you,
>> > >
>> > > Shane Dell
>> > >
>> > >
>> > > On 2023/04/25 21:11:44 "Shearer, Davin" wrote:
>> > > > Hi Mike,
>> > > >
>> > > > Are you running something already that binding to port 9000, like
>> > > Portainer?
>> > > >
>> > > > -Davin
>> > > >
>> > > > On 4/25/23, 5:03 PM, "Mike Beckerle" <[email protected]> wrote:
>> > > >
>> > > >     I am not getting off the ground. I set out to evaluate this rc1.
>> > > >
>> > > >     I uninstalled the existing 1.2.0 visx. I installed the 1.3.0-rc1
>> > > visx. I
>> > > >     restarted VSCode.
>> > > >
>> > > >     I am trying to debug into PCAP. PCAP uses, via a jar file, the
>> > > ethernetIP
>> > > >     DFDL schema as a component.
>> > > >
>> > > >     I deleted the old and created a new launch.json.
>> > > >
>> > > >     I manually entered the jar file for ethernetIP jar into
>> > > debuggerClasspath.
>> > > >
>> > > >     I go to the Run and Debug sidebar. Then I choose and run the
>> "ask
>> > > for file
>> > > >     name" configuration.
>> > > >
>> > > >     I specify the main pcap schema file.
>> > > >
>> > > >     I specify a data file.
>> > > >
>> > > >     I get this error pop up:
>> > > >
>> > > >     The terminal process "/bin/bash '--login', '-c',
>> > './daffodil-debugger
>> > > >     --listenPort 4711'" terminated with exit code: 1.
>> > > >
>> > > >     The Terminal Window has:
>> > > >
>> > > >     [ERROR] [04/25/2023 16:51:41.540]
>> > > >     [omega-grpc-akka.actor.internal-dispatcher-2]
>> > > >     [akka://omega-grpc/system/IO-TCP/selectors/$a/0] Bind failed for
>> > TCP
>> > > >     channel on endpoint [/127.0.0.1:9000]
>> > > >     java.net.BindException: [/127.0.0.1:9000] Address already in
>> use
>> > > >             at java.base/sun.nio.ch.Net.bind0(Native Method)
>> > > >             at java.base/sun.nio.ch.Net.bind(Net.java:459)
>> > > >
>> > > >
>> > > > -----------------------------------------------------------------
>> > > > This message and any files transmitted within are intended
>> > > > solely for the addressee or its representative and may contain
>> > > > company proprietary information.  If you are not the intended
>> > > > recipient, notify the sender immediately and delete this
>> > > > message.  Publication, reproduction, forwarding, or content
>> > > > disclosure is prohibited without the consent of the original
>> > > > sender and may be unlawful.
>> > > >
>> > > > Concurrent Technologies Corporation and its Affiliates.
>> > > > www.ctc.com  1-800-282-4392
>> > > > -----------------------------------------------------------------
>> > > >
>> > >
>> >
>>
>

Reply via email to