Hoping to find the source of this error

5 Messages

Chris Saunders-4

Reply Threaded

I have a multithreaded application and I am frequently getting this error:

index_large_enough: Assertion violated. (CHECK_VIOLATION)

******************************** Thread exception
*****************************

In thread Root thread 0x0 (thread id)

****************************************************************************
***

----------------------------------------------------------------------------
---

Class / Object Routine Nature of exception
Effect

----------------------------------------------------------------------------
---

ARRAYED_LIST remove @11 index_large_enough:

<00000000038E5E18> Runtime check violated.
Fail

----------------------------------------------------------------------------
---

ARRAYED_LIST remove @6

<00000000038E5E18> Routine failure.
Fail

----------------------------------------------------------------------------
---

EV_APPLICATION_IMP windows @11

<00000000038D2878> Routine failure.
Fail

----------------------------------------------------------------------------
---

MANDOLIN3_APPLICATION

windows @2

<00000000038D2848> (From EV_APPLICATION) Routine failure.
Fail

----------------------------------------------------------------------------
---

Invalid_object increase_action_sequence_call_counter

windows_not_void:

<0000000000000000> (From EV_APPLICATION) Class invariant violated.
Fail

----------------------------------------------------------------------------
---

MANDOLIN3_APPLICATION

increase_action_sequence_call_counter @1

<00000000038D2848> (From EV_APPLICATION) Routine failure.
Fail

----------------------------------------------------------------------------
---

EV_NOTIFY_ACTION_SEQUENCE

call @2

<00000000038D2A28> (From EV_LITE_ACTION_SEQUENCE)

Routine failure.
Fail

----------------------------------------------------------------------------
---

EV_APPLICATION_IMP process_event_queue @15

<00000000038D2878> (From EV_APPLICATION_I)

Routine failure.
Fail

----------------------------------------------------------------------------
---

Call stack:

ObjectClassRoutine

------------------

[0x3D07218] ARRAYED_LIST remove ( @ 6 )

[0x3D07228] EV_APPLICATION_IMP windows ( @ 11 )

[0x3D07230] MANDOLIN3_APPLICATION windows (From EV_APPLICATION) ( @ 2 )

[0x3D07230] MANDOLIN3_APPLICATION increase_action_sequence_call_counter
(From EV_APPLICATION) ( @ 1 )

[0x3D07238] EV_NOTIFY_ACTION_SEQUENCE call (From EV_LITE_ACTION_SEQUENCE) (
@ 2 )

[0x3D07228] EV_APPLICATION_IMP process_event_queue (From EV_APPLICATION_I)
<R> ( @ 15 )

[0x3D07228] EV_APPLICATION_IMP launch (From EV_APPLICATION_I) ( @ 3 )

[0x3D07230] MANDOLIN3_APPLICATION launch (From EV_APPLICATION) <R> ( @ 4 )

[0x3D07230] MANDOLIN3_APPLICATION make_and_launch ( @ 4 )

It seems this problem comes and goes as I add or remove calls to
"do_once_on_idle" from EV_APPLICATION. I'm not including the feature here
because it is a little long. I'm hoping that someone may be able to assist
given the information above. I have done a fair number of programs before
that have had similar problems but I have not come up with anything that is
sure to solve them as I have never figured out exactly what was causing
this.

Regards

Chris Saunders

[Non-text portions of this message have been removed]

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/eiffel_software/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:eiffel_software-digest@...
mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

rfo

RE: Hoping to find the source of this error

Reply Threaded

Hi Chris!

It sure looks like you have more than one thread accessing the list, and
therefore changing the state of the list out from under each other.
The data structure is not thread safe, so you need to add your own
controls (mutexes, condition vars, etc) to ensure safe access and
predictable state. If you have relatively few entry points into the
list, then you can wrap those accesses in your own functions with
appropriate mutexes.
Remove is just a bit more obvious than other operations. Traversal will
also exhibit odd behavior, but you might not be noticing it. You would
see incorrect items in that case, rather than an off-the-end-of-earth
behavior as in your example.

R

==================================================
Roger F. Osmond
----------------------------------------
Amalasoft Corporation
273 Harwood Avenue
Littleton, MA 01460

> -------- Original Message --------
> Subject: [eiffel_software] Hoping to find the source of this error
> From: "Chris Saunders" <evas@...>
> Date: Fri, July 11, 2008 3:35 am
> To: <eiffel_software@...>
> I have a multithreaded application and I am frequently getting this error:
>
> index_large_enough: Assertion violated. (CHECK_VIOLATION)
> ******************************** Thread exception
> *****************************
> In thread Root thread 0x0 (thread id)
> ****************************************************************************
> ***
> ----------------------------------------------------------------------------
> ---
> Class / Object Routine Nature of exception
> Effect
> ----------------------------------------------------------------------------
> ---
> ARRAYED_LIST remove @11 index_large_enough:
> <00000000038E5E18> Runtime check violated.
> Fail
> ----------------------------------------------------------------------------
> ---
> ARRAYED_LIST remove @6
> <00000000038E5E18> Routine failure.
> Fail
> ----------------------------------------------------------------------------
> ---
> EV_APPLICATION_IMP windows @11
> <00000000038D2878> Routine failure.
> Fail
> ----------------------------------------------------------------------------
> ---
> MANDOLIN3_APPLICATION
> windows @2
> <00000000038D2848> (From EV_APPLICATION) Routine failure.
> Fail
> ----------------------------------------------------------------------------
> ---
> Invalid_object increase_action_sequence_call_counter
> windows_not_void:
> <0000000000000000> (From EV_APPLICATION) Class invariant violated.
> Fail
> ----------------------------------------------------------------------------
> ---
> MANDOLIN3_APPLICATION
> increase_action_sequence_call_counter @1
> <00000000038D2848> (From EV_APPLICATION) Routine failure.
> Fail
> ----------------------------------------------------------------------------
> ---
> EV_NOTIFY_ACTION_SEQUENCE
> call @2
> <00000000038D2A28> (From EV_LITE_ACTION_SEQUENCE)
> Routine failure.
> Fail
> ----------------------------------------------------------------------------
> ---
> EV_APPLICATION_IMP process_event_queue @15
> <00000000038D2878> (From EV_APPLICATION_I)
> Routine failure.
> Fail
> ----------------------------------------------------------------------------
> ---
>
> Call stack:
>
> ObjectClassRoutine
> ------------------
> [0x3D07218] ARRAYED_LIST remove ( @ 6 )
> [0x3D07228] EV_APPLICATION_IMP windows ( @ 11 )
> [0x3D07230] MANDOLIN3_APPLICATION windows (From EV_APPLICATION) ( @ 2 )
> [0x3D07230] MANDOLIN3_APPLICATION increase_action_sequence_call_counter
> (From EV_APPLICATION) ( @ 1 )
> [0x3D07238] EV_NOTIFY_ACTION_SEQUENCE call (From EV_LITE_ACTION_SEQUENCE) (
> @ 2 )
> [0x3D07228] EV_APPLICATION_IMP process_event_queue (From EV_APPLICATION_I)
> <R> ( @ 15 )
> [0x3D07228] EV_APPLICATION_IMP launch (From EV_APPLICATION_I) ( @ 3 )
> [0x3D07230] MANDOLIN3_APPLICATION launch (From EV_APPLICATION) <R> ( @ 4 )
> [0x3D07230] MANDOLIN3_APPLICATION make_and_launch ( @ 4 )
>
> It seems this problem comes and goes as I add or remove calls to
> "do_once_on_idle" from EV_APPLICATION. I'm not including the feature here
> because it is a little long. I'm hoping that someone may be able to assist
> given the information above. I have done a fair number of programs before
> that have had similar problems but I have not come up with anything that is
> sure to solve them as I have never figured out exactly what was causing
> this.
>
> Regards
> Chris Saunders
> [Non-text portions of this message have been removed]

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/eiffel_software/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:eiffel_software-digest@...
mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

Chris Saunders-4

RE: Hoping to find the source of this error

Reply Threaded

As far as I know, I am not making any use of the list - it is some part of the Vision2 code. I am guessing, but am not sure that this has something to do with my use of "do_once_on_idle" when drawing a pixmap. I'm not actually seeing anything that suggests this but for some reason I am suspicious.

Anyway, thanks for the suggestion.

Regards

Chris Saunders

From: eiffel_software@... [mailto:eiffel_software@...] On Behalf Of rfo@...
Sent: Friday, July 11, 2008 9:33 AM
To: eiffel_software@...
Subject: RE: [eiffel_software] Hoping to find the source of this error

Hi Chris!

It sure looks like you have more than one thread accessing the list, and
therefore changing the state of the list out from under each other.
The data structure is not thread safe, so you need to add your own
controls (mutexes, condition vars, etc) to ensure safe access and
predictable state. If you have relatively few entry points into the
list, then you can wrap those accesses in your own functions with
appropriate mutexes.
Remove is just a bit more obvious than other operations. Traversal will
also exhibit odd behavior, but you might not be noticing it. You would
see incorrect items in that case, rather than an off-the-end-of-earth
behavior as in your example.

R

==================================================
Roger F. Osmond
----------------------------------------
Amalasoft Corporation
273 Harwood Avenue
Littleton, MA 01460

> -------- Original Message --------
> Subject: [eiffel_software] Hoping to find the source of this error
> From: "Chris Saunders" <evas@... <mailto:evas%40mountaincable.net> >
> Date: Fri, July 11, 2008 3:35 am
> To: <eiffel_software@... <mailto:eiffel_software%40yahoogroups.com> >
> I have a multithreaded application and I am frequently getting this error:
>
> index_large_enough: Assertion violated. (CHECK_VIOLATION)
> ******************************** Thread exception
> *****************************
> In thread Root thread 0x0 (thread id)
> ****************************************************************************
> ***
> ----------------------------------------------------------
> ---
> Class / Object Routine Nature of exception
> Effect
> ----------------------------------------------------------
> ---
> ARRAYED_LIST remove @11 index_large_enough:
> <00000000038E5E18> Runtime check violated.
> Fail
> ----------------------------------------------------------
> ---
> ARRAYED_LIST remove @6
> <00000000038E5E18> Routine failure.
> Fail
> ----------------------------------------------------------
> ---
> EV_APPLICATION_IMP windows @11
> <00000000038D2878> Routine failure.
> Fail
> ----------------------------------------------------------
> ---
> MANDOLIN3_APPLICATION
> windows @2
> <00000000038D2848> (From EV_APPLICATION) Routine failure.
> Fail
> ----------------------------------------------------------
> ---
> Invalid_object increase_action_sequence_call_counter
> windows_not_void:
> <0000000000000000> (From EV_APPLICATION) Class invariant violated.
> Fail
> ----------------------------------------------------------
> ---
> MANDOLIN3_APPLICATION
> increase_action_sequence_call_counter @1
> <00000000038D2848> (From EV_APPLICATION) Routine failure.
> Fail
> ----------------------------------------------------------
> ---
> EV_NOTIFY_ACTION_SEQUENCE
> call @2
> <00000000038D2A28> (From EV_LITE_ACTION_SEQUENCE)
> Routine failure.
> Fail
> ----------------------------------------------------------
> ---
> EV_APPLICATION_IMP process_event_queue @15
> <00000000038D2878> (From EV_APPLICATION_I)
> Routine failure.
> Fail
> ----------------------------------------------------------
> ---
>
> Call stack:
>
> ObjectClassRoutine
> ------------------
> [0x3D07218] ARRAYED_LIST remove ( @ 6 )
> [0x3D07228] EV_APPLICATION_IMP windows ( @ 11 )
> [0x3D07230] MANDOLIN3_APPLICATION windows (From EV_APPLICATION) ( @ 2 )
> [0x3D07230] MANDOLIN3_APPLICATION increase_action_sequence_call_counter
> (From EV_APPLICATION) ( @ 1 )
> [0x3D07238] EV_NOTIFY_ACTION_SEQUENCE call (From EV_LITE_ACTION_SEQUENCE) (
> @ 2 )
> [0x3D07228] EV_APPLICATION_IMP process_event_queue (From EV_APPLICATION_I)
> <R> ( @ 15 )
> [0x3D07228] EV_APPLICATION_IMP launch (From EV_APPLICATION_I) ( @ 3 )
> [0x3D07230] MANDOLIN3_APPLICATION launch (From EV_APPLICATION) <R> ( @ 4 )
> [0x3D07230] MANDOLIN3_APPLICATION make_and_launch ( @ 4 )
>
> It seems this problem comes and goes as I add or remove calls to
> "do_once_on_idle" from EV_APPLICATION. I'm not including the feature here
> because it is a little long. I'm hoping that someone may be able to assist
> given the information above. I have done a fair number of programs before
> that have had similar problems but I have not come up with anything that is
> sure to solve them as I have never figured out exactly what was causing
> this.
>
> Regards
> Chris Saunders
> [Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/eiffel_software/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:eiffel_software-digest@...
mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

Emmanuel Stapf

RE: Hoping to find the source of this error

Reply Threaded

Are you sure that all vision2 events are treated in the thread in which the vision2 event loop has been started. If it is not the case, then it is expected that nothing would work in a multithreaded environment.

Regards,
Manu

> -----Original Message-----
> From: eiffel_software@...
> [mailto:eiffel_software@...] On Behalf Of Chris Saunders
> Sent: Friday, July 11, 2008 7:03 AM
> To: eiffel_software@...
> Subject: RE: [eiffel_software] Hoping to find the source of this error
>
> As far as I know, I am not making any use of the list - it is some part
> of the Vision2 code. I am guessing, but am not sure that this has
> something to do with my use of "do_once_on_idle" when drawing a pixmap.
> I'm not actually seeing anything that suggests this but for some reason I
> am suspicious.
>
>
>
> Anyway, thanks for the suggestion.
>
>
>
> Regards
>
> Chris Saunders
>
>
>
> From: eiffel_software@...
> [mailto:eiffel_software@...] On Behalf Of rfo@...
> Sent: Friday, July 11, 2008 9:33 AM
> To: eiffel_software@...
> Subject: RE: [eiffel_software] Hoping to find the source of this error
>
>
>
>
> Hi Chris!
>
> It sure looks like you have more than one thread accessing the list, and
> therefore changing the state of the list out from under each other.
> The data structure is not thread safe, so you need to add your own
> controls (mutexes, condition vars, etc) to ensure safe access and
> predictable state. If you have relatively few entry points into the
> list, then you can wrap those accesses in your own functions with
> appropriate mutexes.
> Remove is just a bit more obvious than other operations. Traversal will
> also exhibit odd behavior, but you might not be noticing it. You would
> see incorrect items in that case, rather than an off-the-end-of-earth
> behavior as in your example.
>
> R
>
> ==================================================
> Roger F. Osmond
> ----------------------------------------
> Amalasoft Corporation
> 273 Harwood Avenue
> Littleton, MA 01460
>
> > -------- Original Message --------
> > Subject: [eiffel_software] Hoping to find the source of this error
> > From: "Chris Saunders" <evas@...
> <mailto:evas%40mountaincable.net> >
> > Date: Fri, July 11, 2008 3:35 am
> > To: <eiffel_software@...
> <mailto:eiffel_software%40yahoogroups.com> >
> > I have a multithreaded application and I am frequently getting this
> error:
> >
> > index_large_enough: Assertion violated. (CHECK_VIOLATION)
> > ******************************** Thread exception
> > *****************************
> > In thread Root thread 0x0 (thread id)
> >
> *************************************************************************
> ***
> > ***
> > ----------------------------------------------------------
> > ---
> > Class / Object Routine Nature of exception
> > Effect
> > ----------------------------------------------------------
> > ---
> > ARRAYED_LIST remove @11 index_large_enough:
> > <00000000038E5E18> Runtime check violated.
> > Fail
> > ----------------------------------------------------------
> > ---
> > ARRAYED_LIST remove @6
> > <00000000038E5E18> Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > EV_APPLICATION_IMP windows @11
> > <00000000038D2878> Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > MANDOLIN3_APPLICATION
> > windows @2
> > <00000000038D2848> (From EV_APPLICATION) Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > Invalid_object increase_action_sequence_call_counter
> > windows_not_void:
> > <0000000000000000> (From EV_APPLICATION) Class invariant violated.
> > Fail
> > ----------------------------------------------------------
> > ---
> > MANDOLIN3_APPLICATION
> > increase_action_sequence_call_counter @1
> > <00000000038D2848> (From EV_APPLICATION) Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > EV_NOTIFY_ACTION_SEQUENCE
> > call @2
> > <00000000038D2A28> (From EV_LITE_ACTION_SEQUENCE)
> > Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > EV_APPLICATION_IMP process_event_queue @15
> > <00000000038D2878> (From EV_APPLICATION_I)
> > Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> >
> > Call stack:
> >
> > ObjectClassRoutine
> > ------------------
> > [0x3D07218] ARRAYED_LIST remove ( @ 6 )
> > [0x3D07228] EV_APPLICATION_IMP windows ( @ 11 )
> > [0x3D07230] MANDOLIN3_APPLICATION windows (From EV_APPLICATION) ( @ 2 )
> > [0x3D07230] MANDOLIN3_APPLICATION increase_action_sequence_call_counter
> > (From EV_APPLICATION) ( @ 1 )
> > [0x3D07238] EV_NOTIFY_ACTION_SEQUENCE call (From
> EV_LITE_ACTION_SEQUENCE) (
> > @ 2 )
> > [0x3D07228] EV_APPLICATION_IMP process_event_queue (From
> EV_APPLICATION_I)
> > <R> ( @ 15 )
> > [0x3D07228] EV_APPLICATION_IMP launch (From EV_APPLICATION_I) ( @ 3 )
> > [0x3D07230] MANDOLIN3_APPLICATION launch (From EV_APPLICATION) <R> ( @
> 4 )
> > [0x3D07230] MANDOLIN3_APPLICATION make_and_launch ( @ 4 )
> >
> > It seems this problem comes and goes as I add or remove calls to
> > "do_once_on_idle" from EV_APPLICATION. I'm not including the feature
> here
> > because it is a little long. I'm hoping that someone may be able to
> assist
> > given the information above. I have done a fair number of programs
> before
> > that have had similar problems but I have not come up with anything
> that is
> > sure to solve them as I have never figured out exactly what was causing
> > this.
> >
> > Regards
> > Chris Saunders
> > [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

------------------------------------------------------------------------
Eiffel Software
805-685-1006
http://www.eiffel.com
Customer support: http://support.eiffel.com
User group: http://groups.eiffel.com/join
------------------------------------------------------------------------

Chris Saunders-4

RE: Hoping to find the source of this error

Reply Threaded

Hey Manu. I am not sure where the Vision2 event loop is started, I'm guessing that it is in the application class. What I am trying to do is use the "do_once_on_idle" procedure called from "MAIN_WINDOW" to update an "EV_PIXMAP" and the text on an "EV_LABEL" that is on an "EV_STATUS_BAR". I use "EV_ENFIRONMENT" to acquire the application object.

I haven't seen any documentation on how to properly do multithreading in a Vision2 application and so am mostly guessing about what I am doing.

If your not to busy to provide some help it would be very appreciated.

Regards

Chris Saunders

From: eiffel_software@... [mailto:eiffel_software@...] On Behalf Of Emmanuel Stapf [ES]
Sent: Tuesday, July 15, 2008 12:15 AM
To: eiffel_software@...
Subject: RE: [eiffel_software] Hoping to find the source of this error

Are you sure that all vision2 events are treated in the thread in which the vision2 event loop has been started. If it is not the case, then it is expected that nothing would work in a multithreaded environment.

Regards,
Manu

> -----Original Message-----
> From: eiffel_software@... <mailto:eiffel_software%40yahoogroups.com>
> [mailto:eiffel_software@... <mailto:eiffel_software%40yahoogroups.com> ] On Behalf Of Chris Saunders
> Sent: Friday, July 11, 2008 7:03 AM
> To: eiffel_software@... <mailto:eiffel_software%40yahoogroups.com>
> Subject: RE: [eiffel_software] Hoping to find the source of this error
>
> As far as I know, I am not making any use of the list - it is some part
> of the Vision2 code. I am guessing, but am not sure that this has
> something to do with my use of "do_once_on_idle" when drawing a pixmap.
> I'm not actually seeing anything that suggests this but for some reason I
> am suspicious.
>
>
>
> Anyway, thanks for the suggestion.
>
>
>
> Regards
>
> Chris Saunders
>
>
>
> From: eiffel_software@... <mailto:eiffel_software%40yahoogroups.com>
> [mailto:eiffel_software@... <mailto:eiffel_software%40yahoogroups.com> ] On Behalf Of rfo@... <mailto:rfo%40amalasoft.com>
> Sent: Friday, July 11, 2008 9:33 AM
> To: eiffel_software@... <mailto:eiffel_software%40yahoogroups.com>
> Subject: RE: [eiffel_software] Hoping to find the source of this error
>
>
>
>
> Hi Chris!
>
> It sure looks like you have more than one thread accessing the list, and
> therefore changing the state of the list out from under each other.
> The data structure is not thread safe, so you need to add your own
> controls (mutexes, condition vars, etc) to ensure safe access and
> predictable state. If you have relatively few entry points into the
> list, then you can wrap those accesses in your own functions with
> appropriate mutexes.
> Remove is just a bit more obvious than other operations. Traversal will
> also exhibit odd behavior, but you might not be noticing it. You would
> see incorrect items in that case, rather than an off-the-end-of-earth
> behavior as in your example.
>
> R
>
> ==================================================
> Roger F. Osmond
> ----------------------------------------
> Amalasoft Corporation
> 273 Harwood Avenue
> Littleton, MA 01460
>
> > -------- Original Message --------
> > Subject: [eiffel_software] Hoping to find the source of this error
> > From: "Chris Saunders" <evas@... <mailto:evas%40mountaincable.net>
> <mailto:evas%40mountaincable.net> >
> > Date: Fri, July 11, 2008 3:35 am
> > To: <eiffel_software@... <mailto:eiffel_software%40yahoogroups.com>
> <mailto:eiffel_software%40yahoogroups.com> >
> > I have a multithreaded application and I am frequently getting this
> error:
> >
> > index_large_enough: Assertion violated. (CHECK_VIOLATION)
> > ******************************** Thread exception
> > *****************************
> > In thread Root thread 0x0 (thread id)
> >
> *************************************************************************
> ***
> > ***
> > ----------------------------------------------------------
> > ---
> > Class / Object Routine Nature of exception
> > Effect
> > ----------------------------------------------------------
> > ---
> > ARRAYED_LIST remove @11 index_large_enough:
> > <00000000038E5E18> Runtime check violated.
> > Fail
> > ----------------------------------------------------------
> > ---
> > ARRAYED_LIST remove @6
> > <00000000038E5E18> Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > EV_APPLICATION_IMP windows @11
> > <00000000038D2878> Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > MANDOLIN3_APPLICATION
> > windows @2
> > <00000000038D2848> (From EV_APPLICATION) Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > Invalid_object increase_action_sequence_call_counter
> > windows_not_void:
> > <0000000000000000> (From EV_APPLICATION) Class invariant violated.
> > Fail
> > ----------------------------------------------------------
> > ---
> > MANDOLIN3_APPLICATION
> > increase_action_sequence_call_counter @1
> > <00000000038D2848> (From EV_APPLICATION) Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > EV_NOTIFY_ACTION_SEQUENCE
> > call @2
> > <00000000038D2A28> (From EV_LITE_ACTION_SEQUENCE)
> > Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> > EV_APPLICATION_IMP process_event_queue @15
> > <00000000038D2878> (From EV_APPLICATION_I)
> > Routine failure.
> > Fail
> > ----------------------------------------------------------
> > ---
> >
> > Call stack:
> >
> > ObjectClassRoutine
> > ------------------
> > [0x3D07218] ARRAYED_LIST remove ( @ 6 )
> > [0x3D07228] EV_APPLICATION_IMP windows ( @ 11 )
> > [0x3D07230] MANDOLIN3_APPLICATION windows (From EV_APPLICATION) ( @ 2 )
> > [0x3D07230] MANDOLIN3_APPLICATION increase_action_sequence_call_counter
> > (From EV_APPLICATION) ( @ 1 )
> > [0x3D07238] EV_NOTIFY_ACTION_SEQUENCE call (From
> EV_LITE_ACTION_SEQUENCE) (
> > @ 2 )
> > [0x3D07228] EV_APPLICATION_IMP process_event_queue (From
> EV_APPLICATION_I)
> > <R> ( @ 15 )
> > [0x3D07228] EV_APPLICATION_IMP launch (From EV_APPLICATION_I) ( @ 3 )
> > [0x3D07230] MANDOLIN3_APPLICATION launch (From EV_APPLICATION) <R> ( @
> 4 )
> > [0x3D07230] MANDOLIN3_APPLICATION make_and_launch ( @ 4 )
> >
> > It seems this problem comes and goes as I add or remove calls to
> > "do_once_on_idle" from EV_APPLICATION. I'm not including the feature
> here
> > because it is a little long. I'm hoping that someone may be able to
> assist
> > given the information above. I have done a fair number of programs
> before
> > that have had similar problems but I have not come up with anything
> that is
> > sure to solve them as I have never figured out exactly what was causing
> > this.
> >
> > Regards
> > Chris Saunders
> > [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>