gmane.editors.winedt

Access violation when trying to build tree or set main file

Dear List,

the following problem occurs on WinEdt 5.6 Beta, it also occured on WinEdt 5.5 (even on a freshly installed, after reinstalling windows etc.):

When klick on the symbol "Set Main File" I get the following error message:

---
An Exception Occured while executing a macro:
Line: [CMD('Set Main File');BuildTree;]
---

From the project menu I figure that the file is set (as I can select "Remove Main File"), yet, when I try to build the tree, I get an:

---
Invalid pointer operation.
---

As I said, the problem can be reproduced on 5.5 and 5.6. Every now an then I get an access violation:

---
Acces violation at address 00402214 in module 'WinEdt.exe'. Write of
address 00000021.
---

This turns into a loop, so I need to kill WinEdt through task manager...

Any suggestions, and, did anybody encounter the same problem? I have had it on 2 Computers, running Windows Vista 32-bit (Home Premium / Ultimate).
Please let me know if you need more information.

Best regards,

Jan-Henrik

MSN Video: Videoclips im Messenger? Ausprobieren und gemeinsam Spaß haben!

headers

Nicolas Vaughan | 23 Aug 18:27

Re: Access violation when trying to build tree or set main file

Hi Jan-Henrik,
Where are your %b and %B directories placed? Perhaps your paths are too long for it to be handled properly by WinEdt...
Cheers,
Nicolas Vaughan

On Sat, Aug 23, 2008 at 6:07 AM, Jan-Henrik Horstmann <jhorstma <at> hotmail.com> wrote:

Dear List,

the following problem occurs on WinEdt 5.6 Beta, it also occured on WinEdt 5.5 (even on a freshly installed, after reinstalling windows etc.):

When klick on the symbol "Set Main File" I get the following error message:

---
An Exception Occured while executing a macro:
Line: [CMD('Set Main File');BuildTree;]
---

From the project menu I figure that the file is set (as I can select "Remove Main File"), yet, when I try to build the tree, I get an:

---
Invalid pointer operation.
---

As I said, the problem can be reproduced on 5.5 and 5.6. Every now an then I get an access violation:

---
Acces violation at address 00402214 in module 'WinEdt.exe'. Write of
address 00000021.
---

This turns into a loop, so I need to kill WinEdt through task manager...

Any suggestions, and, did anybody encounter the same problem? I have had it on 2 Computers, running Windows Vista 32-bit (Home Premium / Ultimate).
Please let me know if you need more information.

Best regards,

Jan-Henrik

MSN Video: Videoclips im Messenger? Ausprobieren und gemeinsam Spaß haben!

headers

Jan-Henrik Horstmann | 23 Aug 18:46

RE: Access violation when trying to build tree or set main file

Hey Nicolas,

The %B: "C:\Program Files\WinEdt"

The %b: The same, I guess, since I did not allow for user folders during installation...

So, that can't be it, can it? Also, I tested working on the files when they are in my user-folder because the path to my files is actually kind of long, but that didn't change anything...
:-(

It's strange...
And what is even more strange: Every now and then the tree is created without an error message... In other cases, I think it's created, too, as I can click on it, but it's not displayed (files will open, when I click in the "white space"...)

HELP! :-)

Thanks for the first idea!

Greetings,

Jan-Henrik

Date: Sat, 23 Aug 2008 11:27:09 -0500
From: nivaca <at> gmail.com
To: winedt+list <at> wsg.net
Subject: Re: [WinEdt] Access violation when trying to build tree or set main file

Hi Jan-Henrik,
Where are your %b and %B directories placed? Perhaps your paths are too long for it to be handled properly by WinEdt...
Cheers,
Nicolas Vaughan

On Sat, Aug 23, 2008 at 6:07 AM, Jan-Henrik Horstmann <jhorstma <at> hotmail.com> wrote:

Dear List,

the following problem occurs on WinEdt 5.6 Beta, it also occured on WinEdt 5.5 (even on a freshly installed, after reinstalling windows etc.):

When klick on the symbol "Set Main File" I get the following error message:

---
An Exception Occured while executing a macro:
Line: [CMD('Set Main File');BuildTree;]
---

From the project menu I figure that the file is set (as I can select "Remove Main File"), yet, when I try to build the tree, I get an:

---
Invalid pointer operation.
---

As I said, the problem can be reproduced on 5.5 and 5.6. Every now an then I get an access violation:

---
Acces violation at address 00402214 in module 'WinEdt.exe'. Write of
address 00000021.
---

This turns into a loop, so I need to kill WinEdt through task manager...

Any suggestions, and, did anybody encounter the same problem? I have had it on 2 Computers, running Windows Vista 32-bit (Home Premium / Ultimate).
Please let me know if you need more information.

Best regards,

Jan-Henrik

MSN Video: Videoclips im Messenger? Ausprobieren und gemeinsam Spaß haben!

Wahre Stärke kommt von innen – welcher Athlet steckt in Dir?

headers

Jan-Henrik Horstmann | 23 Aug 19:11

RE: Access violation when trying to build tree or set main file

oO

I just "downgraded" to 5.5 and it seems to work perfectly well...?! STRANGE.

However, I will not touch anything and leave it running... At least Alex knows that there's something wrong, at least with 5.6. Yes, Beta, but the same problems definately occured on 5.5, too. The only thing I changed on the 5.5 install: I allowed for a user folder creation. Could that be a source of error?

Greetings and thank you for opinions.

Jan-Henrik

From: jhorstma <at> hotmail.com
To: winedt+list <at> wsg.net
Date: Sat, 23 Aug 2008 18:46:59 +0200
Subject: RE: [WinEdt] Access violation when trying to build tree or set main file

.ExternalClass .EC_hmmessage P {padding:0px;} .ExternalClass body.EC_hmmessage {font-size:10pt;font-family:Tahoma;}

Hey Nicolas,

The %B: "C:\Program Files\WinEdt"

Hi Jan-Henrik,
Where are your %b and %B directories placed? Perhaps your paths are too long for it to be handled properly by WinEdt...
Cheers,
Nicolas Vaughan

On Sat, Aug 23, 2008 at 6:07 AM, Jan-Henrik Horstmann <jhorstma <at> hotmail.com> wrote:

Dear List,

the following problem occurs on WinEdt 5.6 Beta, it also occured on WinEdt 5.5 (even on a freshly installed, after reinstalling windows etc.):

When klick on the symbol "Set Main File" I get the following error message:

---
An Exception Occured while executing a macro:
Line: [CMD('Set Main File');BuildTree;]
---

From the project menu I figure that the file is set (as I can select "Remove Main File"), yet, when I try to build the tree, I get an:

---
Invalid pointer operation.
---

As I said, the problem can be reproduced on 5.5 and 5.6. Every now an then I get an access violation:

---
Acces violation at address 00402214 in module 'WinEdt.exe'. Write of
address 00000021.
---

This turns into a loop, so I need to kill WinEdt through task manager...

Any suggestions, and, did anybody encounter the same problem? I have had it on 2 Computers, running Windows Vista 32-bit (Home Premium / Ultimate).
Please let me know if you need more information.

Best regards,

Jan-Henrik

MSN Video: Videoclips im Messenger? Ausprobieren und gemeinsam Spaß haben!

Wahre Stärke kommt von innen – welcher Athlet steckt in Dir?
MSN Video: Videoclips im Messenger? Ausprobieren und gemeinsam Spaß haben!

headers

Jan-Henrik Horstmann | 24 Aug 11:03

RE: Access violation when trying to build tree or set main file

A new day, the problem is back - on WinEdt 5.5!

Even more strange...

I disabled "Reopen last project" to be able to at least launch WinEdt, opening a file, building a tree and setting it as main file works then. But once I try to open a project I get the error message again.

Am I the only one? As I've already written, problem occured on 2 computers, with various versions...

Kind regards

Jan-Henrik

From: jhorstma <at> hotmail.com
To: winedt+list <at> wsg.net
Subject: RE: [WinEdt] Access violation when trying to build tree or set main file
Date: Sat, 23 Aug 2008 19:11:10 +0200

.ExternalClass .EC_hmmessage P {padding:0px;} .ExternalClass body.EC_hmmessage {font-size:10pt;font-family:Tahoma;}

Hey Nicolas,

The %B: "C:\Program Files\WinEdt"

Hi Jan-Henrik,
Where are your %b and %B directories placed? Perhaps your paths are too long for it to be handled properly by WinEdt...
Cheers,
Nicolas Vaughan

On Sat, Aug 23, 2008 at 6:07 AM, Jan-Henrik Horstmann <jhorstma <at> hotmail.com> wrote:

Dear List,

the following problem occurs on WinEdt 5.6 Beta, it also occured on WinEdt 5.5 (even on a freshly installed, after reinstalling windows etc.):

When klick on the symbol "Set Main File" I get the following error message:

---
An Exception Occured while executing a macro:
Line: [CMD('Set Main File');BuildTree;]
---

From the project menu I figure that the file is set (as I can select "Remove Main File"), yet, when I try to build the tree, I get an:

---
Invalid pointer operation.
---

As I said, the problem can be reproduced on 5.5 and 5.6. Every now an then I get an access violation:

---
Acces violation at address 00402214 in module 'WinEdt.exe'. Write of
address 00000021.
---

This turns into a loop, so I need to kill WinEdt through task manager...

Any suggestions, and, did anybody encounter the same problem? I have had it on 2 Computers, running Windows Vista 32-bit (Home Premium / Ultimate).
Please let me know if you need more information.

Best regards,

Jan-Henrik

MSN Video: Videoclips im Messenger? Ausprobieren und gemeinsam Spaß haben!

Wahre Stärke kommt von innen – welcher Athlet steckt in Dir?
MSN Video: Videoclips im Messenger? Ausprobieren und gemeinsam Spaß haben!
Trete mit Deinem inneren Athleten in Verbindung. Beantworte die Fragen!

headers

WinEdt Team | 25 Aug 22:48

Re: Access violation when trying to build tree or set main file

> the following problem occurs on WinEdt 5.6 Beta, it also
> occured on WinEdt 5.5 (even on a freshly installed, after
> reinstalling windows etc.):
>
> When klick on the symbol "Set Main File" I get the following
> error message:
>
> ---
> An Exception Occured while executing a macro: Line: [CMD('Set
> Main File');BuildTree;]
> ---
>
> From the project menu I figure that the file is set (as I can
> select "Remove Main File"), yet, when I try to build the tree,
> I get an:
>
> ---
> Invalid pointer operation.
> ---
>
> As I said, the problem can be reproduced on 5.5 and 5.6. Every
> now an then I get an access violation:
>
> ---
> Acces violation at address 00402214 in module 'WinEdt.exe'.
> Write of address 00000021.
> ---
>
> This turns into a loop, so I need to kill WinEdt through task
> manager...
>
>
> Any suggestions, and, did anybody encounter the same problem? I
> have had it on 2 Computers, running Windows Vista 32-bit (Home
> Premium / Ultimate). Please let me know if you need more
> information.

I did not hear from other users and I cannot reproduce this on
any of my machines.

Start a new Project (test.prj). Open a few files from WinEdt's
Documents>Samples Menu and set Thesis.tex (sample) as a main
file. Build/ delete tree a few times. Any Crash?

Restart WinEdt. Crash when it reloads the files and builds the
tree? Does tree respond to clicks etc...?

If there are no crashes open one of your main files that you
have been previously working on. Repeat the procedure.

Keep on trying until you come with a reproducible situation.
Describe exactly what I should do to get the same crash (and
possibly send me the main file because it is possible that
there is something in your sources that triggers a problem).

If I can reproduce a crash I'll fix it otherwise I don't have
enough information to do anything about it.

I am assuming that you are using default configuration and you
did not make any changes to tree.ini. If you did you should
take that into account as well.

I am inclined to believe that it is something in your sources
that triggers the problem or else some custom modification to
tree.ini. If you want this fixed you should do some
investigating and then present me with a reproducible problem.
Then I can fire up a debugger and see what's wrong. And only
then it can be fixed. The above addresses don't help...

I cannot guess what exactly you are doing. Anything I should
know about your use of Unicode/ UTF-8 (in text or in
filenames)?

best regards,

alex

headers

Jan-Henrik Horstmann | 26 Aug 02:26

RE: Access violation when trying to build tree or set main file

Alex,

I know and totally understand that you need more and better information on the problem - I will follow your advises on investigating further this coming weekend.

By the way, yes, I'm using UTF-8 files (created following the instructions in the manual), BUT, when the problem first appeared I figured it might have something to do with that an tried plain ansi-files - same problem. However, as I said, I will try again and see if I can get to a reproducable situation.

More later.

Thanks for now.

Jan-Henrik

> Date: Mon, 25 Aug 2008 17:48:05 -0300
> From: support <at> winedt.com
> To: winedt+list <at> wsg.net
> Subject: Re: [WinEdt] Access violation when trying to build tree or set main file
>
> > the following problem occurs on WinEdt 5.6 Beta, it also
> > occured on WinEdt 5.5 (even on a freshly installed, after
> > reinstalling windows etc.):
> >
> > When klick on the symbol "Set Main File" I get the following
> > error message:
> >
> > ---
> > An Exception Occured while executing a macro: Line: [CMD('Set
> > Main File');BuildTree;]
> > ---
> >
> > From the project menu I figure that the file is set (as I can
> > select "Remove Main File"), yet, when I try to build the tree,
> > I get an:
> >
> > ---
> > Invalid pointer operation.
> > ---
> >
> > As I said, the problem can be reproduced on 5.5 and 5.6. Every
> > now an then I get an access violation:
> >
> > ---
> > Acces violation at address 00402214 in module 'WinEdt.exe'.
> > Write of address 00000021.
> > ---
> >
> > This turns into a loop, so I need to kill WinEdt through task
> > manager...
> >
> >
> > Any suggestions, and, did anybody encounter the same problem? I
> > have had it on 2 Computers, running Windows Vista 32-bit (Home
> > Premium / Ultimate). Please let me know if you need more
> > information.
>
> I did not hear from other users and I cannot reproduce this on
> any of my machines.
>
> Start a new Project (test.prj). Open a few files from WinEdt's
> Documents>Samples Menu and set Thesis.tex (sample) as a main
> file. Build/ delete tree a few times. Any Crash?
>
> Restart WinEdt. Crash when it reloads the files and builds the
> tree? Does tree respond to clicks etc...?
>
> If there are no crashes open one of your main files that you
> have been previously working on. Repeat the procedure.
>
> Keep on trying until you come with a reproducible situation.
> Describe exactly what I should do to get the same crash (and
> possibly send me the main file because it is possible that
> there is something in your sources that triggers a problem).
>
> If I can reproduce a crash I'll fix it otherwise I don't have
> enough information to do anything about it.
>
> I am assuming that you are using default configuration and you
> did not make any changes to tree.ini. If you did you should
> take that into account as well.
>
> I am inclined to believe that it is something in your sources
> that triggers the problem or else some custom modification to
> tree.ini. If you want this fixed you should do some
> investigating and then present me with a reproducible problem.
> Then I can fire up a debugger and see what's wrong. And only
> then it can be fixed. The above addresses don't help...
>
> I cannot guess what exactly you are doing. Anything I should
> know about your use of Unicode/ UTF-8 (in text or in
> filenames)?
>
> best regards,
>
> alex
>

MSN Video: Videoclips im Messenger? Ausprobieren und gemeinsam Spaß haben!

headers

Jan-Henrik Horstmann | 27 Aug 21:37

RE: Access violation when trying to build tree or set main file

Dear Alex,

I've tried, and I think I succeeded... Here's what I did:

> Date: Mon, 25 Aug 2008 17:48:05 -0300
> From: support <at> winedt.com
> To: winedt+list <at> wsg.net
> Subject: Re: [WinEdt] Access violation when trying to build tree or set main file
>
> > the following problem occurs on WinEdt 5.6 Beta, it also
> > occured on WinEdt 5.5 (even on a freshly installed, after
> > reinstalling windows etc.):
> >
> > When klick on the symbol "Set Main File" I get the following
> > error message:
> >
> > ---
> > An Exception Occured while executing a macro: Line: [CMD('Set
> > Main File');BuildTree;]
> > ---
> >
> > From the project menu I figure that the file is set (as I can
> > select "Remove Main File"), yet, when I try to build the tree,
> > I get an:
> >
> > ---
> > Invalid pointer operation.
> > ---
> >
> > As I said, the problem can be reproduced on 5.5 and 5.6. Every
> > now an then I get an access violation:
> >
> > ---
> > Acces violation at address 00402214 in module 'WinEdt.exe'.
> > Write of address 00000021.
> > ---
> >
> > This turns into a loop, so I need to kill WinEdt through task
> > manager...
> >
> >
> > Any suggestions, and, did anybody encounter the same problem? I
> > have had it on 2 Computers, running Windows Vista 32-bit (Home
> > Premium / Ultimate). Please let me know if you need more
> > information.
>
> I did not hear from other users and I cannot reproduce this on
> any of my machines.
>
> Start a new Project (test.prj). Open a few files from WinEdt's
> Documents>Samples Menu and set Thesis.tex (sample) as a main
> file. Build/ delete tree a few times. Any Crash?

No crash

> Restart WinEdt. Crash when it reloads the files and builds the
> tree? Does tree respond to clicks etc...?

No crash, everything works

> If there are no crashes open one of your main files that you
> have been previously working on. Repeat the procedure.

Did that, worked a couple times, but then the problem reoccured... (That's what is so strange)

> Keep on trying until you come with a reproducible situation.
> Describe exactly what I should do to get the same crash (and
> possibly send me the main file because it is possible that
> there is something in your sources that triggers a problem).

I have not been able to make it "reproducable", all I can say is that the problem occured every now and then, without me changing anything in the config, nor in the files themselves.

> If I can reproduce a crash I'll fix it otherwise I don't have
> enough information to do anything about it.

I understand that.

> I am assuming that you are using default configuration and you
> did not make any changes to tree.ini. If you did you should
> take that into account as well.

No, I love WinEdt, but I'm not that advanced yet. :-)

> I am inclined to believe that it is something in your sources
> that triggers the problem or else some custom modification to
> tree.ini. If you want this fixed you should do some
> investigating and then present me with a reproducible problem.

I did some investigation: I opened all my .tex files in a different editor (Notepad++) and checked the file format: Some were UTF-8 with BOM, some without, and some were even ANSI.
(Note: All my files of course include " % !Mode:: "TeX:UTF-8" ")
What I did then: Converted all my files to UTF-8 with BOM, so that they are "definately" UTF-8 and detected as such, no matter what.

Result: The error occured as before. :-(

BUT, then I think I found a solution. When I save my main file in ANSI format, it appears to be working just well! No crashes so far, rebuilding, opening, closing, it all works flawlessly...

So, I can definately live with that, the main file is just there for loading all my other files, so I don't need Unicode in that.
And to make sure XeLaTeX doesn't get confused I put in a little \XeTeXinputencoding "UTF-8"

> Then I can fire up a debugger and see what's wrong. And only
> then it can be fixed. The above addresses don't help...

I was aware of that, and it was frustrating because I knew you wouldn't be able to help. Sorry I was not able to give more information.

> I cannot guess what exactly you are doing. Anything I should
> know about your use of Unicode/ UTF-8 (in text or in
> filenames)?

Yes. Unicode. AND, I use a "precompiled preamble" (http://magic.aladdin.cs.cmu.edu/2007/11/02/precompiled-preamble-for-latex/)
Thus the first line of my main file MUST be: %&mastersthesis
(Where mastersthesis is the name of my precompiled preamble)

Anyway, it appears to be working fine now, so I'm happy. And even this is a very particular problem, maybe it will help other users with UTF-8

Trete mit Deinem inneren Athleten in Verbindung. Beantworte die Fragen!

headers

Aleksander Simonic | 30 Aug 20:33

Re: Access violation when trying to build tree or set main file

Let's keep this private.

I've never asked you the following:

1. Was the main file opened when the crash occurred?

2. What language are you using?

3. Do you use any Unicode characters in filenames?

4. Are all your input directives in the main file or do
subfiles contain further inclusions?

5. The crash always occurs when you are working with a
particular main file or is this a problem that persists for all
your projects?

Once the file is loaded UTF8 format shouldn't matter anymore.

I am really puzzled by this... Perhaps I should take a look at
your main file (in UTF-8 format) and see if I can detect
anything out of the ordinary.

The solution that works for now might just be a temporary thing
if there is a problem elsewhere... There appears to be some
kind of a memory allocation problem but I am still at a loss as
to why, where, etc...

best regards,

alex

headers

Jan-Henrik Horstmann | 31 Aug 10:44

RE: Access violation when trying to build tree or set main file

.hmmessage P { margin:0px; padding:0px } body.hmmessage { FONT-SIZE: 10pt; FONT-FAMILY:Tahoma } > Let's keep this private.

Yes, sorry I was "bothering" the list with a specific topic like this...

> I've never asked you the following:
>
> 1. Was the main file opened when the crash occurred?
Yes and no. In fact, the crash occurs in different situations. It appeared when I tried to build the tree while it was open, and it also appeared when I just double clicked on the project file to open WinEdt.

> 2. What language are you using?
English, German, French

> 3. Do you use any Unicode characters in filenames?
No, all filenames are in lowercase, no special characters, not even spaces: 01_chaper_one.tex, 02_chapter_on_winedt.tex

> 4. Are all your input directives in the main file or do
> subfiles contain further inclusions?
They are all in the main file, except for some listings I load later. (The listings stuff was added long AFTER the problem already occured, so it can't be the source)

> 5. The crash always occurs when you are working with a
> particular main file or is this a problem that persists for all
> your projects?
I have been able to reproduce it on a test file this morning, and was about to send it to you, when the problem started to disappear again?! Up to that point, what I have been able to reproduce: The problem occurs when the main file is in UTF-8 without BOM. Once it is in UTF-8 with BOM, the problem disappears. I have been able to "play" with that, changing the format with a different editor and then trying to load it.

I have also been able to the same thing on my "real" project - that also is working fine again now. The error is reproducable for some time, then it disappears... It is so strange.

> Once the file is loaded UTF8 format shouldn't matter anymore.
>
> I am really puzzled by this... Perhaps I should take a look at
> your main file (in UTF-8 format) and see if I can detect
> anything out of the ordinary.
Unfortunately my "real" project is to some degree confidential, so I can't just send you the files to have a look at them.
As I have been able to provoke the problem on a sample case this morning, I will keep on trying to get a file that does not work, and then send you a snapshot right away.
Sorry for that.
(

> The solution that works for now might just be a temporary thing
> if there is a problem elsewhere... There appears to be some
> kind of a memory allocation problem but I am still at a loss as
> to why, where, etc...
So far it's working perfectly fine... I'll keep you updated.

I'm sorry for not being able to come up with a "this is it". But I'm curious, too, now, and I'll keep on trying. For now I've gotta "work" though. Need to hand in my thesis soon. :-)

Kind regards

Jan-Henrik

Online Karaoke: Neu! Kostenlos! Hunderte Songs zum Mitsingen!

headers

Arcady Novosyolov | 31 Aug 10:56

Re: Access violation when trying to build tree or set main file

2008/8/31 Jan-Henrik Horstmann <jhorstma <at> hotmail.com>

> Let's keep this private.

Yes, sorry I was "bothering" the list with a specific topic like this...

Please keep exchanging via list, it's interesting. Thanks.

Arcady

headers

WinEdt Team | 4 Sep 21:49

Re: Access violation when trying to build tree or set main file

> > The solution that works for now might just be a temporary thing
> > if there is a problem elsewhere... There appears to be some
> > kind of a memory allocation problem but I am still at a loss as
> > to why, where, etc...
> So far it's working perfectly fine... I'll keep you updated.
>
> I'm sorry for not being able to come up with a "this is it".
> But I'm curious, too, now, and I'll keep on trying. For now
> I've gotta "work" though. Need to hand in my thesis soon. 

Although I was not able to reproduce the crash I did some
investigating (focusing on a UTF-8 format and absence of BOM).
As it turns out WinEdt moved 1-byte too many when loading a
UTF-8 document for purpose of building a tree AND a document
did not contain a BOM AND the document was actually ASCII (it
contained no multi-byte characters). Usually 1-byte in a large
memory segment should not cause an Access Violation because
Windows tends to round-up memory allocations. However, an
access violation could arise under certain circumstances (this
would explain why it was not always reproducible)...

Anyway, if I am correct then the problem is fixed for the next
version. There was also a discrepancy with freeing memory after
converting a UTF-8 document. This one would result in small
memory leaks. This, too, has now been fixed. WinEdt's (limited)
UTF-8 capabilities have not been extensively tested by many
users. That's why your problem is not widely experienced by
others. It was worth taking a second look at the code, though.

Best regards,

alex

headers

Jan-Henrik Horstmann | 7 Sep 09:05

RE: Access violation when trying to build tree or set main file

> Date: Thu, 4 Sep 2008 16:49:46 -0300
> From: support <at> winedt.com
> To: winedt+list <at> wsg.net
> Subject: Re: [WinEdt] Access violation when trying to build tree or set main file
>
> > > The solution that works for now might just be a temporary thing
> > > if there is a problem elsewhere... There appears to be some
> > > kind of a memory allocation problem but I am still at a loss as
> > > to why, where, etc...
> > So far it's working perfectly fine... I'll keep you updated.
> >
> > I'm sorry for not being able to come up with a "this is it".
> > But I'm curious, too, now, and I'll keep on trying. For now
> > I've gotta "work" though. Need to hand in my thesis soon. :-)

>
> Although I was not able to reproduce the crash I did some
> investigating (focusing on a UTF-8 format and absence of BOM).
> As it turns out WinEdt moved 1-byte too many when loading a
> UTF-8 document for purpose of building a tree AND a document
> did not contain a BOM AND the document was actually ASCII (it
> contained no multi-byte characters). Usually 1-byte in a large
> memory segment should not cause an Access Violation because
> Windows tends to round-up memory allocations. However, an
> access violation could arise under certain circumstances (this
> would explain why it was not always reproducible)...

I'm a mechanical/system engineer and not a computer guru, but your explaination sounds reasonable. :-)

> Anyway, if I am correct then the problem is fixed for the next
> version. There was also a discrepancy with freeing memory after
> converting a UTF-8 document. This one would result in small

I'm looking forward to it. So far all is working well, no problems whatsoever. Hence, I will stick to the status quo of my "running system" and not play around. I'll keep on giving feedback though in case I can come up with a reproducable version of the problem - when I have time to look at it in October/November...

> memory leaks. This, too, has now been fixed. WinEdt's (limited)
> UTF-8 capabilities have not been extensively tested by many
> users. That's why your problem is not widely experienced by
> others. It was worth taking a second look at the code, though.
>
> Best regards,
>
> alex
>

I was aware of that and thus used Emacs for some time. Finally switched back to WinEdt when I realized it was working fine... And I'm happy if I can help improving it despite the fact that I'm unfortunately not so much into software programming.

Anyway, thank you for the "support" and keep up the great work.

Kind regrads,

Jan-Henrik

Neu: Office Live Workspace, der kostenlose Online-Arbeitsbereich für Office. Ideal auch für Teams. Jetzt ausprobieren!