the result of the run with gdb is:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x7fff5f38
0x0001001500c4 in gee_linked_list_node_free (self=0x103ff67a0) at
linkedlist.c:1182
1182static void gee_linked_list_node_free
> Thanks, I will try that as soon as I can get my hands on a Linux box,
> i.e. by next week-end (installing "nemiver" on a Mac, results in too
> many unmet dependencies).
Gdb should work equally well.
___
vala-list mailing list
vala-list@gnome.org
http:
Thanks, I will try that as soon as I can get my hands on a Linux box,
i.e. by next week-end (installing "nemiver" on a Mac, results in too
many unmet dependencies).
I' ll keep you posted.
Thanks a lot for the help,
Serge.
On Mon, Jun 13, 2011 at 8:37 AM, Nor Jaidi Tuah
wrote:
>
>> So it must
> So it must be something else.
>
> Perhaps there are memory leaks in libgee (or even in glib2) ?
> Perhaps HashMaps or other Vala containers or dynamically allocated
> objects have a maximal size ?
Try compiling with --debug and
run the program under nemiver.
When it crashes, view the stack tr
On Mon, Jun 13, 2011 at 4:10 AM, Nor Jaidi Tuah
wrote:
> I suspect there is a very long "word" that StringBuilder
> cannot handle. My guess is the crash happens here:
>> word.append_c(c);
>
It seemed like a possible explanation, so I checked it.
I added a "word" length counter which
I suspect there is a very long "word" that StringBuilder
cannot handle. My guess is the crash happens here:
> word.append_c(c);
The long word contains non-alnum. So the test !isalnum
would chop it to smaller pieces amiable to StringBuilder.
hand
Nor Jaidi Tuah
_
In the code hereunder, in the while loop (simple scanner), when I
substitute !isalnum() by Posix.isspace(), the application crashes when
given a very large text file (170 MB) as argument.
Yet it works with !isalnum() instead of isspace().
Also it the application does not crash in either cases whe
