[gstreamer-bugs] [Bug 334715] core dump switching between 32 bit and 64 bit

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=334715
 GStreamer | gstreamer (core) | Ver: 0.10.1


Michael Smith changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO




------- Comment #4 from Michael Smith  2006-03-20 11:46 UTC -------
Can you retest with a recent core (0.10.4, or cvs)? I rewrote the
registry-writing code to actually check that writes worked; also the registry
reading code should now never abort, no matter how badly corrupted the registry
is, so the worst case will be that it'll end up doing registry rebuilds that it
shouldn't need.

If that doesn't help, I really have no idea - if you could run a debugger and
figure out where the bad writes are coming from that would be helpful.

Also, really, you should have completely independent registry files for 32 and
64 bit modes (you might have quite a different set of plugins available), the
registry file should be called registry.arch.xml (with 'arch' replaced by some
architecture name - I get 'i486' or 'i686' depending on how gstreamer has been
built, for instance), you should have a similar distinction for 32/64 bit mode.
Maybe that wasn't in 0.10.1, though.

Anyway, since a) the bug will hopefully be gone, and b) current core should
have two different reasons to never trigger this case if the bug _isn't_ gone,
I expect this is fine now.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.