Subject | Re: [IBO] Re: Access Violations |
---|---|
Author | Jason Wharton |
Post date | 2001-08-14T23:43:55Z |
What these AV's seem to come from is all the new background things that are
going on at design-time.
Ever since they added in the explorer/treview thing I'v had a hard time with
things that otherwise are coded perfectly.
Take for example the latest. I had a component performing a Locate() on a
dataset. When doing this if it doesn't find a match in memory it will put
together a query that does the locate on the server. If there isn't an
object already instantiated to do this query it will dynamically create one
internally. Then it does the locate and on it goes. However, inside of the
constructor the Delphi IDE got a hook that for some reason made the object
inspector think it needed to read all the component values again. What ended
up happening is code to do the same locate got called again. Because the
constructor hadn't finished yet it attempted to instantiate a new instance
of the locate query. Thus, it was in a loop until it crashed. Also, it
really made a mess of the memory calling a constructor multiple times for
one instance.
I've found that design-time coding is like walking through a mine field.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
going on at design-time.
Ever since they added in the explorer/treview thing I'v had a hard time with
things that otherwise are coded perfectly.
Take for example the latest. I had a component performing a Locate() on a
dataset. When doing this if it doesn't find a match in memory it will put
together a query that does the locate on the server. If there isn't an
object already instantiated to do this query it will dynamically create one
internally. Then it does the locate and on it goes. However, inside of the
constructor the Delphi IDE got a hook that for some reason made the object
inspector think it needed to read all the component values again. What ended
up happening is code to do the same locate got called again. Because the
constructor hadn't finished yet it attempted to instantiate a new instance
of the locate query. Thus, it was in a loop until it crashed. Also, it
really made a mess of the memory calling a constructor multiple times for
one instance.
I've found that design-time coding is like walking through a mine field.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
----- Original Message -----
From: "John Tomaselli" <jrt@...>
To: <IBObjects@yahoogroups.com>
Sent: Tuesday, August 14, 2001 3:46 PM
Subject: RE: [IBO] Re: Access Violations
> And I thought I was the only one!
>
> -----Original Message-----
> From: Kevin Stanton [mailto:Kevin.Stanton@...]
> Sent: Tuesday, August 14, 2001 9:53 AM
> To: IBObjects@yahoogroups.com
> Subject: RE: [IBO] Re: Access Violations
>
>
> I'm on 3.xx and get them quite a lot. Hope to see these resolved in V4!
> Kevin
> -----Original Message-----
> From: Mario Zimmermann [mailto:mail@...]
> Sent: Tuesday, August 14, 2001 3:34 AM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] Re: Access Violations
>
>
> I got these access violations over and over again in BCB5 and IBO3.xx.
>
> In IBO 4.2Ea it is much better but still not completely solved.
>
> Mario
>
>
> --- In IBObjects@y..., rod@m... wrote:
> > Since I installed IBO ver 4.2Ea (my app was in 3.xx) ( D5 )I get at
> random
> > times ?Access violation at address 044E49F1 in Module
> ?IBO40CRT_D5.BPL?
> > read of address 00000000?. This is very annoying. Have I not
> installed
> > something that that module may need ?
> >
> > Thanks - Rod
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>