FYI I added the comment to description and replaced the previous version with 3.1.1 upload

Hi All,

We reached 1800 files on the archives! Thanks to all the developers and uploaders!

@AMIGASYSTEM,

The syntax file is looking for four files; exec.doc, intuition.doc, graphics.doc, and dos.doc in a docs directory located wherever you tell it to look. I changed the location to Development:Bin and added the docs directory with blank files of those names and get no more error messages but still get syntax highlighting. So it works fine with those adjustments.

The one bug I noticed, however, was that every time you use the mouse wheel and scroll past the bottom of the file you are editing you get a guru. That makes it pretty dangerous to use so I'm conditioning myself to not use the mouse wheel. That bug does not occur on the OS3 version. Thanks.

NathanH

Sorry NathanH, I don't understand from the translation which software you are talking about!

I crosscompiled for Aros 64 bit and it start with the message "SEGLENGTH too short" (see shot 1 for complete message).
So i disable the code that check this SEGLENGHT and after running it it Segfault.
On the second shot is the session with GDB active...that tell to look at AllocSegment () at AnnBaseFunc.c line 62 where is


ALLOCPOOL is defined as
#define ALLOCPOOL AllocPooled(linePool,SEGLENGTH+4)

SEGLENGHT is defined as
#define SEGLENGTH 32
//allocSegment() uses SEGLENGTH+4

Anyone has some advices to make it work?

Farox, even in my compilation on AROS One, I had that message when running it from the Shell or from Icona with CLI in Tooltypes.

If, on the other hand, you run it normally from Icona on Wanderer, you don't get any message. If it works properly, it should open a File Request to load a document.

@AMIGASYSTEM

Sorry, I was talking about how to get rid of the annoying syntax highlighting requestors in the new Annotate and still allow syntax highlighting.

Nathan

Ok i know it...what i was asking (with the shot of GDB ) is some expert to check why this code don't work on 64 bit, and if its possible to fix.

@All

I think it would make sense to continue the discussion on Annotate debugging into a separate thread as this can take several posts which are not related with AROS Archives management.

@Farox

The issue you are seeing is an efffect of memory corruption - for example some part of program writting into memory that it didn't allocate or writting beyong allocaged memory. The standard approach I use in such cases is to comment out all functionality from main() and confirm that issue is not happening. Then I uncomment functionality step by step until the issue starts happening again. This way I get the smallest amount of code needed to trigger then issue. Then I review this limited code and try to analyze/hunt for which part of that limited code is actually causing the issue.

There is also a brute-force method: you convert all ULONG local variables (or program structures fields) to IPTR and see if that solves the crash. If such then you need to find out which exact variable needed to be converted and which can stay as ULONG. This may or may not work of course.

Deadwood on WCS package I forgot to include the catalogs, I need to replace it

Ok, approved the new package.

thank you

The manual also had to be included, that's why I replaced it as well