Import Project hangs on

When you select on a directory and click OK to start the import process, the application generates a glibc error message:

*** glibc detected *** free(): invalid pointer: 0xb7985d80 ***

Thanks for the bug report - did you get the "inform developers" (bug-buddy) dialog? If so, could you please paste it's output in here? If not, would you please follow the instructions on https://wiki.ubuntu.com/DebuggingProgramCrash to get a stack trace, so we could try to give the information to the anjuta developers? It might help if you supplied us with a link to the very project you tried to import. Thanks a lot.

It is not a program crash. The program freezes (I tried on 2 computers) and the reason is in the error message I have reported: in the source code (when clicking OK on the FileSelector to import a project), a non-allocated pointer is freed. I believe this information is enough for the developer to get the wrong code line.
It happens on EVERY project you try to import. I didn't realize before, as I am not used to import projects: I prefer to start from scratch.

I am attaching here an strace until I got the application frozen. Then I had to kill it. The problem is clear: a wrong pointer address has been sent to a free() call.

I can confirm this bug in Anjuta 1.2.4 (running under Ubuntu 5.10 in my case).

The bug strikes only when you use the file selector dialog to chose the directory of the project to be imported. If you enter the path manually instead of clicking 'Browse', the import works fine.

I have been told (but have not verified yet) that similar freezes occur on other "select directory" operations, e.g. when chosing an include path?

As you saw the dialog when it couldn't import project, It was because Ubuntu used gnome-build 0.1.2.
I downloaded gnome-build 0.1.3 source from debian and installed it. and I tried to open the .prj file of the project which I wanted to import. And it did import!
it's been almost 1 year later since the last post. I hope this helps anyway.

So, is this still a problem on Edgy/Dapper?

Fabio, you say it hangs even though you get a glibc error ? If you still get a glibc error, can you please follow http://wiki.ubuntu.com/DebuggingProgramCrash to get a backtrace ?

Sorry Vassilis, but I have removed long time ago anjuta from my system
as I am not using it anymore.

Fabio

On 8/29/06, Vassilis Pandis <email address hidden> wrote:
> Fabio, you say it hangs even though you get a glibc error ? If you still
> get a glibc error, can you please follow
> http://wiki.ubuntu.com/DebuggingProgramCrash to get a backtrace ?
>
> --
> Import Project hangs on
> https://launchpad.net/bugs/2575
>

Can anyone else confirm that this problem still exists?

I believe this problem is related to (on Edgy)

/usr/bin/anjuta_import.sh

# Template file is in data dir, so:
# TEMPLATE="$(dirname $0)/anjuta_project.template"
TEMPLATE="@PACKAGE_DATA_DIR@/anjuta_project.template"

@PACKAGE_DATA_DIR@ should've been expanded to:

/usr/share/anjuta

The filename is:

/usr/share/anjuta/anjuta_project.template

perhaps this is just part of the problem...

I did this to fix it:

cat /usr/bin/anjuta_import.sh | sed -e 's,@PACKAGE_DATA_DIR@,/usr/share/anjuta,' > /tmp/anjuta_import.sh

it worked

Do you still have this issue with the new releases of anjuta ? Thank you.

Hi Jerome,

thanks for keeping track of this. Unfortunately I don't have an update,
since I have not used my Linux computer for quite a while, due to lack of
time.

Regards,
Jürgen

On Tue, 26 Feb 2008 19:31:55 +0100, Jérôme Guelfucci
<email address hidden> wrote:

> Do you still have this issue with the new releases of anjuta ? Thank
> you.
>
> ** Changed in: anjuta (Ubuntu)
> Assignee: MOTU (motu) => (unassigned)
> Status: Confirmed => Incomplete
>

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!