We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 536 - Blitting from one portion of a surface to another side shuts down SDL
Summary: Blitting from one portion of a surface to another side shuts down SDL
Status: RESOLVED DUPLICATE of bug 699
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 1.2.13
Hardware: x86 Windows (XP)
: P2 major
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords: target-1.2.14
Depends on:
Blocks:
 
Reported: 2008-01-05 17:28 UTC by Steve Allen
Modified: 2009-09-14 10:43 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Allen 2008-01-05 17:28:55 UTC
I am using a large surface (like 4200 x 4200) the side portions are used as a sort of palette to grab objects from that will be displayed on the portion sent to the screen.  SDL 1.2.9 and below all handled this flawlessly - but 1.2.13 shuts the program down with no error message. This only appears to happen when I blit from 1 part of a bitmap to another part.  The rest of my blits all work perfectly.

e.x.  SDL_blit(sourcesurf, destsurf, ...)  and sourcesurf and destsurf are the same surface. The strange part is that SDL offers no error and just shuts down quietly.  

I have not been able to try this on any version between 1.2.9 and 1.2.13.
Comment 1 Ryan C. Gordon 2009-09-13 16:33:31 UTC
Tagging this bug with "target-1.2.14" so we can try to resolve it for SDL 1.2.14.

Please note that we may choose to resolve it as WONTFIX. This tag is largely so we have a comprehensive wishlist of bugs to examine for 1.2.14 (and so we can close bugs that we'll never fix, rather than have them live forever in Bugzilla).

--ryan.
Comment 2 Patrice Mandin 2009-09-14 10:43:05 UTC
I think this is a duplicate for #699

*** This bug has been marked as a duplicate of bug 699 ***