StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWeird and unpredictable crash when using libx264 cross-compiled with MinGW
primarykey
Id
9240782
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2012-02-11T14:00:51.903
FavoriteCount
0
LastActivityDate
2012-03-02T19:57:46.837
LastEditDate
2012-02-18T12:58:39.500
LastEditorUserId
63661
OwnerUserId
63661
ParentId
0
PostTypeId
1
Score
3
ViewCount
1197
LastEditorDisplayName
text
Body
I'm working on a C++ project using Visual Studio 2010 on Windows. I'm linking dynamically against x264 which I built myself as a shared library using MinGW following the guide at <a href="http://www.ayobamiadewole.com/Blog/Others/x264compilation.aspx" rel="nofollow">http://www.ayobamiadewole.com/Blog/Others/x264compilation.aspx</a> The strange thing is that my x264 code is working perfectly sometimes. Then when I change some line of code (or even change the comments in the file!) and recompile everything crashes on the line <pre><code>encoder_ = x264_encoder_open(&param); </code></pre> With the message <pre><code>Access violation reading location 0x00000000 </code></pre> I'm not doing anything funky at all so it's probably not my code that is wrong but I guess there is something going wrong with the linking or maybe something is wrong with how I compiled x264. The full initialization code: <pre><code>x264_param_t param = { 0 }; if (x264_param_default_preset(&param, "ultrafast", "zerolatency") < 0) { throw KStreamerException("x264_param_default_preset failed"); } param.i_threads = 1; param.i_width = 640; param.i_height = 480; param.i_fps_num = 10; param.i_fps_den = 1; encoder_ = x264_encoder_open(&param); // <----- if (encoder_ == 0) { throw KStreamerException("x264_encoder_open failed"); } x264_picture_alloc(&pic_, X264_CSP_I420, 640, 480); </code></pre> Edit: It turns out that it always works in Release mode and when using superfast instead of ultrafast it also works in Debug mode 100%. Could it be that the ultrafast mode is doing some crazy optimizations that the debugger doesn't like?
Tags
<c++><visual-c++><linker><mingw><libx264>
Title
Weird and unpredictable crash when using libx264 cross-compiled with MinGW
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDaniel
UserOwnerUserId
1. USDaniel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POWeird and unpredictable crash when using libx264 cross-compiled with MinGW
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWeird and unpredictable crash when using libx264 cross-compiled with MinGW
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.