Bug 3386 - [Gtk] Crash in convertScreenToBase
Summary: [Gtk] Crash in convertScreenToBase
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-02-10 14:36 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-04-04 20:02 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Mikayla Hutchinson [MSFT] 2012-02-10 14:36:53 UTC
received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0xd0000020
0x90d16d47 in objc_msgSend ()
(gdb) t a a bt
<...>
Thread 1 (process 87487):
#0  0x90d16d47 in objc_msgSend ()
#1  0x00000000 in ?? ()
(gdb) thread 1
[Switching to thread 1 (process 87487), "com.apple.main-thread"]
0x90d16d47 in objc_msgSend ()
(gdb) p/x $eax
$1 = 0xffba4f0
(gdb) x/s $ecx
0x96ee3244 <__PRETTY_FUNCTION__.186541+3028>:	 "convertScreenToBase:"
Comment 1 Mikayla Hutchinson [MSFT] 2012-04-04 20:02:16 UTC
This hasn't been reported again, assuming it was memory corruption from another bug.