Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 34365 - Neither Anjuta 1.1.97 nor 1.1.98 will open files on an amd64 box
Summary: Neither Anjuta 1.1.97 nor 1.1.98 will open files on an amd64 box
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: AMD64 Project
Depends on:
Reported: 2003-11-25 14:45 UTC by Darryl Bleau
Modified: 2003-12-01 14:52 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Darryl Bleau 2003-11-25 14:45:11 UTC
Anjuta crashes when trying to open any file, either from a project or on it's own.

Reproducible: Always
Steps to Reproduce:
1. set overlays so that you can emerge anjuta 1.1.97 or 1.1.98
2. emerge anjuta
3. try to open a file

Actual Results:  
Pops up the gnome error window. Says:

Application "anjuta" (process XXXXX) has crashed due to a fatal error.
(Segmentation fault).

Expected Results:  
Opened the file for editing :)

Not sure how I can get more information on the crash. I tried to run it in a
terminal but it doesn't give any additional information.

Also to note, anjuta 1.0.2 works flawlessly.
Comment 1 foser (RETIRED) gentoo-dev 2003-11-25 15:08:06 UTC
1.1 is a devel series. Don't expect it to work especially not ona platform like amd64, it's p.mask-ed for a reason.

Comment 2 Darryl Bleau 2003-12-01 11:26:38 UTC
Update on this bug, I sent the anjuta devs a backtrace and they think they have the issue cornered, something to do with a problem with 64 bit pointers. Hopefully, this will be resolved in anjuta 1.2.0 which is due out.. well.. anytime now. So I'm not sure whether to leave this bug open or resolve it to upstream or something else or what.
Comment 3 foser (RETIRED) gentoo-dev 2003-12-01 14:52:42 UTC
resolve upstream should be ok. If you can provide a link to the bug that would be good and maybe add another comment/reopen when it gets fixed or released (don't think we get around to checking the bug on a daily basis ;)).