Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 7 of 7 total |
AV in server |
Wed, Oct 10 2007 1:09 AM | Permanent Link |
Roland Verrinder | Hello
Win2K; Delphi 7 Pro; DBISAM C/S 4.24 Build 1 and 4.25 Build 7; EurekaLog 4.6.7 I have been trying to trace an AV that occurs in the BDISAM server (both ours and the one shipped) when terminating the server when there is still an active connection. This only occurs when: 1) The connected client has entered edit mode and posted a record (wether modified or not). 2) The server has at least one trigger event handler (even with no code). The AV appears to occur during memory cleanup while using either the DBISAM or Delphi memory manager. I have tested with and without EurekaLog active without effect so assume EurekaLog is not the problem. To reproduce: 1) Open the shipped dbsrver server source project in Delphi. 2) Double click a trigger event on the Server Engine and surround the empty handler with remarks to prevent it bing deleted when compiled. 3) Build and compile the server 4) Start the compiled server outside the IDE. 5) Open the shipped dbsys.exe database system utility, logon to the server and open a table. 6) Select a record and enter edit mode. 7) Post the record. 8) Right click the server icon on the task bar, select the Exit option and click yes to the cautionary prompt. A runtime error or AV is then reported. Remove the trigger event handler and repeat steps 3 --> 8 again. All is OK. I have attached a EurekaLog report which puts the AV in the ntdll.dll. An update to DBISAM C/S 4.25 Build 7 has had no effect. The same symtoms also occur on WinXP. Any help much appreciated. Roland Attachments: EurekaLog.txt |
Wed, Oct 10 2007 9:18 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roland,
<< I have been trying to trace an AV that occurs in the BDISAM server (both ours and the one shipped) when terminating the server when there is still an active connection. This only occurs when: >> Thanks for the steps to reproduce the problem. I will look into this and see what I can find. We had a prior report of this from Oliver Bock, but in the EDB release confusion it was not addressed as it should have been. I will ensure that it is taken care of. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Oct 10 2007 6:24 PM | Permanent Link |
Roland Verrinder | <I will ensure that
it is taken care of.> Thanks Tim Look forward to hearing what you find. Roland |
Thu, Nov 1 2007 5:28 PM | Permanent Link |
Roland Verrinder | Roland Verrinder <rverrinder@swiftdsl.com.au> wrote:
<<<I will ensure that it is taken care of.>> Thanks Tim Look forward to hearing what you find.> Tim Have there been any developments on this problem? Roland |
Sat, Nov 3 2007 5:57 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roland,
<< Have there been any developments on this problem? >> Not yet. I haven't had a chance to look at it yet due to EDB development. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Dec 10 2007 7:10 PM | Permanent Link |
Roland Verrinder | Tim
<<Not yet. I haven't had a chance to look at it yet due to EDB development.>> It has now been 2 months. When will this be looked at? Roland |
Tue, Dec 11 2007 10:59 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roland,
<< It has now been 2 months. When will this be looked at? >> It will be addressed within the next 2 weeks. The .NET provider release has taken longer than expected, and that has been the main hold-up. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |