X-Received: by 10.107.140.74 with SMTP id o71mr9884183iod.73.1499777415520; Tue, 11 Jul 2017 05:50:15 -0700 (PDT) X-Received: by 10.36.104.200 with SMTP id v191mr132131itb.2.1499777415486; Tue, 11 Jul 2017 05:50:15 -0700 (PDT) Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!188no2370714itx.0!news-out.google.com!f200ni1640itc.0!nntp.google.com!188no2370711itx.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.graphics.apps.gnuplot Date: Tue, 11 Jul 2017 05:50:15 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.11.190.186; posting-account=vQWs9woAAAANG5imAA2PL-bILRE1Gqn0 NNTP-Posting-Host: 69.11.190.186 References: <2f863699-4fca-4abd-a60e-9f787888dc83@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <664f5cb4-9455-41d0-b9fb-b9e234260d23@googlegroups.com> Subject: Re: GnuPlot periodically locks up From: billwright1984@gmail.com Injection-Date: Tue, 11 Jul 2017 12:50:15 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: csiph.com comp.graphics.apps.gnuplot:3689 On Tuesday, July 11, 2017 at 12:51:25 AM UTC-5, Karl Ratzsch wrote: > Am 10.07.2017 um 22:29 schrieb billwright1984@gmail.com: > > I am running Microsoft XP ... and GnuPlot periodically crashes/locks up= . The last time it generated the following in a text file. Any adivce? > >=20 > > > > > > > > >=20 > Several options you can try > * upgrade to win7 (i hope that machine is not connected to the > internet, running XP?) > * upgrade gnuplot (what version is that?) > * post a simple gp script that reproducibly crashes gnuplot on your > machine > * or if you havent one, report when it usually crashes (what > terminal, the plot command, etc.) >=20 > That xml file contains practically zero useful information, as does > the rest of your description. Thanks ... I will try. Sorry that what I sent was not helpful ... when it = crashes the screen says that it captured information regarding the crash in= a file to send out -- and that is the file I sent to you. Not certain why= the program was choosing to record this useless info - but there you go.