ust 2011 21:57
To: delphi@delphi.org.nz
Subject: [DUG] Access Violation
Not sure where to go with this.
I'm sending 3 bytes of data at 38400 baud every 500 ms. If I speed up the
rate to every 250 ms I get
Access Violation at address 004934CA in Mmodule Dyno.exe' Write add
Wallace
I am not sure what SerialPortNG does exactly (are you using it as a
sniffer?) but maybe you could look at an alternative such as AsyncPro
(was Turbopower but now open source) or Async32 (TMSsoftware - costs) or
TComport (free). I have used all these at some time or other with no issues.
Not sure where to go with this.
I'm sending 3 bytes of data at 38400 baud every 500 ms. If I speed up the rate
to every 250 ms I get
Access Violation at address 004934CA in Mmodule Dyno.exe' Write address
00F2
Code
if SerialPortNG.NextClusterSize >= 0 then begin
sRaw:=S
Thanks, the windows messages check box seems to have done the trick.
Cheers,
Dave.
-Original Message-
From: Myles Penlington [mailto:[EMAIL PROTECTED]]
Sent: Friday, 27 October 2000 11:31
To: Multiple recipients of list delphi
Subject: RE: [DUG]: Access Violation - Help please.
I
October 27, 2000 11:25 AM
To: Multiple recipients of list delphi
Subject: Re: [DUG]: Access Violation - Help please.
This happened to me a while back. I virtually couldn't debug because every
time I tried I would get
AV's in bordbk50.dll. A reinstall has fixed my problem. I was using
This happened to me a while back. I virtually couldn't debug because every
time I tried I would get
AV's in bordbk50.dll. A reinstall has fixed my problem. I was using NT 4.
You may want to just check third party packages you are using also.
JED
>>OK, getting really sick of this now... (Ha
OK, getting really sick of this now... (Happens multiple times a day)
Error
Access violation at address 0D34C6FE in module 'bordbk50.dll'. Read of
address 001D8000.
(the numbers may differ)
This occurs when running any app from D5.01 at random. Occurs on Win2000 Pro
and Windows ME.
Afterwards,
This worked fine, thanks
Darren
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Steve Cooney
> Sent: Tuesday, 7 September 1999 12:40 PM
> To: Multiple recipients of list delphi
> Subject: Re: [DUG]: ACCESS VIOLATION
>
>
ipients of list delphi
> Subject: RE: [DUG]: ACCESS VIOLATION
>
> My, admittedly simplistic, understanding is that is a good
> indicator of an uninitialised pointer. I have had D4 give a similar error
> when I have installed a component too early or installed a rough 3rd
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Darren J Gilbertson
Sent: Tuesday, 7 September 1999 08:35
To: Multiple recipients of list delphi
Subject: [DUG]: ACCESS VIOLATION
Help!
Whenever I attempt to create a new form I get the following error
>
> Whenever I attempt to create a new form I get the following error:
>
> Access violation at address 40053F57 in module VCL40.BPL. Read of Address
>
>
> I have rebooted but it still appears. How can I fix this?
Try deleting the projects .dsk file before loading the project or if it
Uninstalling/Reinstalling Delphi might be the fastest option.
--- Darren J Gilbertson <[EMAIL PROTECTED]> wrote:
> Help!
>
> Whenever I attempt to create a new form I get the following error:
>
> Access violation at address 40053F57 in module VCL40.BPL. Read of
> Address
>
>
> I have
> Whenever I attempt to create a new form I get the following error:
> Access violation at address 40053F57 in module VCL40.BPL. Read of Address
>
>
> I have rebooted but it still appears. How can I fix this?
I'm assuming that all three patches are installed on Delphi as these
fixed a
Help!
Whenever I attempt to create a new form I get the following error:
Access violation at address 40053F57 in module VCL40.BPL. Read of Address
I have rebooted but it still appears. How can I fix this?
Darren Gilbertson
--
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Rohit Gupta
> Sent: Friday, 9 July 1999 12:57
> To: Multiple recipients of list delphi
> Subject: Re: [DUG]: Access violation
>
>
> Willie,
>
> if you cant event trac
Willie,
if you cant event track where it is happening, then the easiest way
is to add try/except blocks as follows to all methods..
procedure
begin
try
your normal code
except
raise; // Put break points on each on of these
end;
end;
In fact, I think it should be done by th
I'm receiving one of these when I call the print
method of an R-Builder pro ppReport componenet. If I preview the report first
it's fine, but if I try to print it first I get an access violation.
How do I trace this? - I've tried "stepping
into" the code using the debugger but obviously I
17 matches
Mail list logo
