eagle crashes when performing most operations

[Kishore]

Binary package hint: eagle

In Hardy AMD64 eagle (4.16r2-1) crashes predictably for many operations. For example pick one of the examples and try to rip up all routed tracks at once and the application crashes. The command line output is not descriptive enough and says "Aborted (core dumped)". This never happened with Gutsy i386.

[Kishore (kitts)]

I downloaded the i386 version of 4.16r2 from the hardy repos and installed on a 32bit installation of Gutsy and there were no crashes. So i guess the crash has something to to with the amd64 architecture.

[Kishore (kitts)]

I tried running it with gdb and here is the result. Sorry i do not understand what it means though.

$ gdb /usr/lib/eagle/bin/eagle
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
(gdb) run
Starting program: /usr/lib/eagle/bin/eagle
(no debugging symbols found)
warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGABRT, Aborted.
0xffffe405 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe405 in __kernel_vsyscall ()
#1 0xf7d67335 in raise () from /lib32/libc.so.6
#2 0xf7d68cb1 in abort () from /lib32/libc.so.6
#3 0xf7dab3c5 in ?? () from /lib32/libc.so.6
#4 0xf7e88160 in ?? () from /lib32/libc.so.6
#5 0x08735d00 in ?? ()
#6 0xfffb2af8 in ?? ()
#7 0x0814e63c in ?? ()
#8 0xfffb2c5c in ?? ()
#9 0xfffb2bcc in ?? ()
#10 0x0004ba78 in ?? ()
#11 0x0001b580 in ?? ()
#12 0x0004a6a0 in ?? ()
#13 0xf7e86ff4 in ?? () from /lib32/libc.so.6
#14 0xfffb2c08 in ?? ()
#15 0x088ba880 in ?? ()
#16 0xfffb2b28 in ?? ()
#17 0xf7dac025 in free () from /lib32/libc.so.6
Backtrace stopped: frame did not save the PC
(gdb) quit

[Kishore (kitts)]

I tried installing the Hardy i386 and eagle crashed there as well. So it is not really a amd64 issue. My only choice now is to switch back to Gutsy as it works in there.

[Kishore (kitts)]

On Wednesday 23 April 2008 12:29:50 kitts wrote:
> I tried installing the Hardy i386 and eagle crashed there as well. So it
> is not really a amd64 issue. My only choice now is to switch back to
> Gutsy as it works in there.

After further attempts i can now confirm that it works fine in hardy when
logged into a kde3 session but eagle crashes when operating in a kde4
session. What could be the issue here now? The only possibilities i can think
of are certain changes in environment variables and the window manager. I
tried manages the environment variables but that did not help.
--
Cheers!
Kishore

[barney_1 (szczys)]

I have the same issue.

When running eagle under kde4 it cashes under the following circumstances:
1) Connecting nets in schematic view
2) Switching from schematic to board view and answering yes to automatic board creation.

Program is stable when run under kde3.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 or 9.04?

[Pedro Villavicencio (pedro)]

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!.