Hello,
I've created a bitmap that can be either memory, video or system. I then use create_sub_bitmap() to create sub bitmaps. All is well and everything displays ok.

When I destroy the sub bitmaps all is well for video and memory bitmaps, but when I call destroy_bitmap on the first sub bitmap where the master is of type System Bitmap, the program crashes.

All the pointers are correct as they both display ok and video/memory works fine. My log shows all is well too:

New video bitmap is 0x3d9de0
Bitmap is sub bitmap of master 0x3d9de0 and created image is 0x3dc138
Sub bitmap destroyed 0x3dc138
sheet_grid.bmp:0x3d9de0 destroyed

This is the output for video and memory bitmaps, but when I use system bitmaps it crashes on the first destroy.

Anyone got a clue as to why?

Do you first...

• Destroy the parent?

</li>
Those are my only guesses until you do what Rey says.

Can you post a small sample programme that duplicates the problem?
Not that I can test it myself (system bitmaps are really a Windows thing, as far as Allegro is concerned right now), but others might be able to.

Sure, but you can write a small programme that creates a system bitmap with child and destroys both of those. Does that reproduce the error? If not, start adding things like video bitmaps along with the system bitmaps and see if that makes the error appear, etc...

[edit]I've put some outputting to the screen of the image being deleted and I guess I must be doing something wrong as it looks like the image being destroyed is (bizarrely) a different part of the master image. It is doing this for video and system bitmaps but memory ones are ok. I don't really get this as just before I exit I am ouputting the same images and they display ok!
[/edit]

I've ran debug from MSVC and it is crashing where I said, at: destroy_bitmap(Image). Checking the value of Image (which is a BITMAP pointer) it seems valid to me and it's address matches that when it was created so it's pointing to the same piece of memory:

- Image 0x012f0b20 {w=24 h=24 clip=-1 ...} BITMAP *
w 24 int
h 24 int
clip -1 int
cl 0 int
cr 24 int
ct 0 int
cb 24 int
+ vtable 0x100eaa60 {color_depth=32 mask_color=16711935 unwrite_bank=0x1009524c ...} GFX_VTABLE *
write_bank 0x10095230 void *
read_bank 0x10095230 void *
dat 0x00000000 void *
id 1610612737 unsigned long
extra 0x012f0068 void *
x_ofs 1 int
y_ofs 47 int
seg 35 int
line 0x012f0b60 unsigned char * [0]

I've ran a trace on the code and the call stack is roughly what I would expect, is it of any use?

alld42.dll!10097efd()
[Frames below may be incorrect and/or missing, no symbols loaded for alld42.dll]
alld42.dll!100986d3()
alld42.dll!10038f93()
> anim_without_d.exe!AnimationLibraryFrame::~AnimationLibraryFrame() Line 840 + 0xf bytes C++
anim_without_d.exe!AnimationLibraryFrame::`scalar deleting destructor'() + 0x2b bytes C++
anim_without_d.exe!AnimationLibraryFrames::~AnimationLibraryFrames() Line 922 + 0x35 bytes C++
anim_without_d.exe!AnimationLibraryFrames::`scalar deleting destructor'() + 0x2b bytes C++
anim_without_d.exe!AnimationLibrary::DestroyAll() Line 1015 + 0x33 bytes C++
anim_without_d.exe!AnimationLibrary::~AnimationLibrary() Line 1008 C++
anim_without_d.exe!AnimationLibrary::`scalar deleting destructor'() + 0x2b bytes C++
anim_without_d.exe!_mangled_main() Line 224 + 0x2d bytes C++
alld42.dll!100a8950()
anim_without_d.exe!WinMain(void * hInst=0x00400000, void * hPrev=0x00000000, char * Cmd=0x001423f6, int nShow=1) Line 234 + 0x3b bytes C++
anim_without_d.exe!__tmainCRTStartup() Line 315 + 0x35 bytes C
anim_without_d.exe!WinMainCRTStartup() Line 187 C
kernel32.dll!7c816d4f()
kernel32.dll!7c8399f3()

Neil: again, have you tried to reproduce the problem with a small example programme?
If it's an Allegro problem, which is possible if you are indeed doing things correctly as you say you are, that will be nescessary to hunt down and fix the problem. If it isn't an Allegro problem it can still help you track down the problem.