Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
142 user(s) are online (131 user(s) are browsing Forums)

Members: 2
Guests: 140

jabirulo, Petrol, more...

Support us!

Headlines

 
  Register To Post  

DSI Error on exit
Just popping in
Just popping in


See User information
Hi! I'm writing a tool with mui and ahi.
When i close the program, workbench gives me a DSI (Data Storage Interrupt) Error.
What is this?
Thx!!

Go to top
Re: DSI Error on exit
Just popping in
Just popping in


See User information
The programm try to read/write to an illegal( not allocated) adress. Maybe you have freed memory and try to access this memory.

Go to top
Re: DSI Error on exit
Amigans Defender
Amigans Defender


See User information

ExecSG Team Lead
Go to top
Re: DSI Error on exit
Just can't stay away
Just can't stay away


See User information
@ssolie. Interesting read. Thanks. How is the automated bug tracking system progressing?

AmigaOne X1000.
Radeon RX550

http://www.tinylife.org.uk/
Go to top
Re: DSI Error on exit
Just popping in
Just popping in


See User information
thk you all!!! :)

Go to top
Re: DSI Error on exit
Just popping in
Just popping in


See User information
Correct if i'm wrong: i solved this commenting "dropinterface".
Well, could it be related to the "-lauto" switch I use in gcc, thus Os automatically provides to close libraries, drop interfaces and so on?
Thk you!

Go to top
Re: DSI Error on exit
Home away from home
Home away from home


See User information
Quote:

Correct if i'm wrong: i solved this commenting "dropinterface".
Well, could it be related to the "-lauto" switch I use in gcc, thus Os automatically provides to close libraries, drop interfaces and so on?
Thk you!


The -lauto switch does provide open and closing functions for many of the standard system libraries. You *can* mix your own open library / interface calls with the lauto ones as the lauto code is only brought in if the library and interface are not explictly declared in the code.

You need to be consistant though, only close and drop interfaces that you have explictly opened yourself.

Which dropinterface call was crashing? Was your code crashing inside libauto.a or at your own dropintrface call?

Maybe you dropped the same interface twice?
It's a good idea to set an pointer to NULL after freeing the resource it points to.

eg

IExec->DropInterface(myinterface);
myinterface = NULL;


Go to top
Re: DSI Error on exit
Quite a regular
Quite a regular


See User information
Quote:
broadblues wrote:
Maybe you dropped the same interface twice?
It's a good idea to set an pointer to NULL after freeing the resource it points to.

eg

IExec->DropInterface(myinterface);
myinterface = NULL;


"A good idea"?? IMHO it should be "programming rule"

Back to a quiet home... At last
Go to top
Re: DSI Error on exit
Amigans Defender
Amigans Defender


See User information
Quote:

rebraist wrote:
Correct if i'm wrong: i solved this commenting "dropinterface".
Well, could it be related to the "-lauto" switch I use in gcc, thus Os automatically provides to close libraries, drop interfaces and so on?

I really don't recommend using the "-lauto" feature. Instead, consider always explicitly controlling the resources you need in your programs.

Take a look at AmiWest Lesson 2: Fundamentals where there is some guidance and help to simplify this task.

You don't need to keep track of both the Interface and the Library base pointer because every Interface contains a pointer back to the Library base pointer.

ExecSG Team Lead
Go to top

  Register To Post

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project