First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 100515
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: dotnet <dotnet@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: David Grant <davidgrant@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
mono-1.1.8-icall.diff mono-1.1.8-icall.diff text/plain David Grant 2005-07-27 22:04 0000 433 bytes Details
mono-1.1.8.2-r1.ebuild mono-1.1.8.2-r1.ebuild text/plain David Grant 2005-07-27 22:04 0000 2.32 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 100515 depends on: Show dependency tree
Bug 100515 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-07-27 14:12 0000 
There is a bug in mono which didn't get in in time for 1.1.8.3. It is a really
annoying bug which makes monodevelop practically unusable.

Try using the most recent monodevelop (0.7) and you'll get errors like this all
the time:

** ERROR **: file icall.c: line 2564 (ves_icall_InternalExecute): assertion
failed: (result)

Here's the fix for it:
http://svn.myrealbox.com/viewcvs/trunk/mono/mono/metadata/icall.c?rev=46854&r1=46632&r2=46854

Can someone include a quick patch in the mono ebuild for gentoo? Thanks.

------- Comment #1 From David Grant 2005-07-27 22:04:21 0000 ------- 
Created an attachment (id=64491) [details]
mono-1.1.8-icall.diff

Patch to fix problem with crashing in monodevelop-0.7

------- Comment #2 From David Grant 2005-07-27 22:04:55 0000 ------- 
Created an attachment (id=64492) [details]
mono-1.1.8.2-r1.ebuild

------- Comment #3 From David Grant 2005-07-27 22:07:08 0000 ------- 
Actually mono-1.1.8.3 is out now...but apparently this icall.c fix went in
right
after mono-1.1.8.3 release was made. The change was supposedly made in the mono
svn repository on July 1st, but somehow it didn't make it out, at least that's
what this guy told me on monodevelop IRC.

------- Comment #4 From David Grant 2005-07-27 22:10:57 0000 ------- 
Just checked mono-1.1.8.3 sources right now to confirm. They also don't have
the
fix. Please add this icall fix immediately as it brings much stability to
monodevelop-0.7 and monodevelop's SVN HEAD as well.

------- Comment #5 From David Grant 2005-07-29 09:08:48 0000 ------- 
anybody home?

------- Comment #6 From Peter Johanson (RETIRED) 2005-07-29 09:48:45 0000 ------- 
Actually, no.

I'm sitting in an airport online via GPRS + my phone.

Dev's have lives, when I'm actually back home and have time for dev work, I'll
surely have time to review this. Probably not before then. (:

------- Comment #7 From Peter Johanson (RETIRED) 2005-08-04 11:32:17 0000 ------- 
Ok, I've just commited 1.1.8.3 to portage, which includes this icall fix.
Marking this bug FIXED, please feel free to re-open if you have any further
problems. Thanks.

------- Comment #8 From David Grant 2005-08-04 14:28:30 0000 ------- 
Ok, thanks. Just one note: I think in the einfo statements for monodevelop-0.7
there is some warning that it crashes. Well I think this is irrelevant now
assuming mono-1.1.8.3 is used. Also 0.7 is masked for this reason. Maybe we can
make monodevelop-0.7 depend on =dev-lang/mono-1.1.8.3?

------- Comment #9 From Peter Johanson (RETIRED) 2005-08-04 15:38:21 0000 ------- 
If you read the note fully, it is only refering to crashes related to using
gtk#
1.0 projects, which is *still* not working with 0.7. This issue has been fixed
in MD SVN, but is in no way back portable. That warning's gotta stay for now.
First Last Prev Next    No search results available      Search page      Enter new bug