yagiuda crashes in Ubuntu Intrepid

Bug #312842 reported by MMarking
4
Affects Status Importance Assigned to Milestone
yagiuda (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: yagiuda

*** glibc detected *** ./input: munmap_chunk(): invalid pointer: 0x0804a7c3 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb7f893f4]
./input[0x8048e66]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7f30685]
./input[0x80487d1]
======= Memory map: ========
08048000-0804c000 r-xp 00000000 08:03 5375050 /home/mocha/temp/yagiuda-1.19/src/input
0804c000-0804d000 r--p 00003000 08:03 5375050 /home/mocha/temp/yagiuda-1.19/src/input
0804d000-0804e000 rw-p 00004000 08:03 5375050 /home/mocha/temp/yagiuda-1.19/src/input
098d5000-098f6000 rw-p 098d5000 00:00 0 [heap]
b7f19000-b7f1a000 rw-p b7f19000 00:00 0
b7f1a000-b8072000 r-xp 00000000 08:02 721575 /lib/tls/i686/cmov/libc-2.8.90.so
b8072000-b8074000 r--p 00158000 08:02 721575 /lib/tls/i686/cmov/libc-2.8.90.so
b8074000-b8075000 rw-p 0015a000 08:02 721575 /lib/tls/i686/cmov/libc-2.8.90.so
b8075000-b8078000 rw-p b8075000 00:00 0
b8078000-b809c000 r-xp 00000000 08:02 721730 /lib/tls/i686/cmov/libm-2.8.90.so
b809c000-b809d000 r--p 00023000 08:02 721730 /lib/tls/i686/cmov/libm-2.8.90.so
b809d000-b809e000 rw-p 00024000 08:02 721730 /lib/tls/i686/cmov/libm-2.8.90.so
b80b3000-b80c0000 r-xp 00000000 08:02 720914 /lib/libgcc_s.so.1
b80c0000-b80c1000 r--p 0000c000 08:02 720914 /lib/libgcc_s.so.1
b80c1000-b80c2000 rw-p 0000d000 08:02 720914 /lib/libgcc_s.so.1
b80c2000-b80c6000 rw-p b80c2000 00:00 0
b80c6000-b80e0000 r-xp 00000000 08:02 721209 /lib/ld-2.8.90.so
b80e0000-b80e1000 r-xp b80e0000 00:00 0 [vdso]
b80e1000-b80e2000 r--p 0001a000 08:02 721209 /lib/ld-2.8.90.so
b80e2000-b80e3000 rw-p 0001b000 08:02 721209 /lib/ld-2.8.90.so
bfccd000-bfce2000 rw-p bffeb000 00:00 0 [stack]
Aborted

The above crash occurs every time I run yagiuda's "input" binary and start to input the parameters for my antenna. I also downloaded the source from the author of the package and I have the exact same crash. I think this is a bug in libc in Ubuntu Intrepid.

Revision history for this message
Miloš Mandarić (mandzo18) wrote :

Thanks for reporting! Can you please get a Backtrace and attach it here? https://wiki.ubuntu.com/Backtrace

Revision history for this message
MMarking (cpt-mocha) wrote :
Download full text (6.0 KiB)

Milos,

Here are the outputs of the "input" program running when it crashes while running the backtrace, and below that is the gdb output.

------------------------------------------------------------------------------------------------------------
mocha@mocha-c2d:~$ input
Yagi-Uda antenna analysis programs, version 1.19
Written by Dr. David Kirkby Ph.D. (G8WRB, email:<email address hidden>)

This program asks for length, diameter and position of antenna elements then
writes them to a file you specify. Data is written in m (metres)

Enter any notes on this design (up to 400 characters): test
Enter a filename to write data to testyagi
Enter the centre frequency in MHz 2400
Enter the minimum frequency in MHz 2100
Enter the maximum frequency in MHz 2600
Enter the frequency steps in MHz 50

Data can be entered in imperial (inches) metric (mm) or wavelengths (lambda)
Please enter i (for imperial), m (for metric) or w (for wavelengths). i
Enter the number of elements for the antenna 5
Enter the angular step size in degrees for the gain to be plotted 15
Are all the elements of the same diameter ? y
Enter the diameter of the elements (in "") 0.0625

Enter location of the driven element in "" (wrt. reflector at x=0) 1.21
Enter length of the driven element (in "") 2.42

Enter length of the reflector (in "") 2.6

Enter location of director 1 in "" (wrt. reflector at x=0.0) 2.42
Enter the length of director 1 (in "") 2.2

Enter location of director 2 in "" (wrt. reflector at x=0.0) 3.64
Enter the length of director 2 (in "") 2

Enter location of director 3 in "" (wrt. reflector at x=0.0) 4.84
Enter the length of director 3 (in "") 1.8
*** glibc detected *** input: munmap_chunk(): invalid pointer: 0x0804a7c3 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb7e5a3f4]
input[0x8048e66]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7e01685]
input[0x80487d1]
======= Memory map: ========
08048000-0804c000 r-xp 00000000 08:02 1558124 /usr/bin/input
0804c000-0804e000 rw-p 00003000 08:02 1558124 /usr/bin/input
097e6000-09807000 rw-p 097e6000 00:00 0 [heap]
b7dea000-b7deb000 rw-p b7dea000 00:00 0
b7deb000-b7f43000 r-xp 00000000 08:02 721575 /lib/tls/i686/cmov/libc-2.8.90.so
b7f43000-b7f45000 r--p 00158000 08:02 721575 /lib/tls/i686/cmov/libc-2.8.90.so
b7f45000-b7f46000 rw-p 0015a000 08:02 721575 /lib/tls/i686/cmov/libc-2.8.90.so
b7f46000-b7f49000 rw-p b7f46000 00:00 0
b7f49000-b7f6d000 r-xp 00000000 08:02 721730 /lib/tls/i686/cmov/libm-2.8.90.so
b7f6d000-b7f6e000 r--p 00023000 08:02 721730 /lib/tls/i686/cmov/libm-2.8.90.so
b7f6e000-b7f6f000 rw-p 00024000 08:02 721730 /lib/tls/i686/cmov/libm-2.8.90.so
b7f84000-b7f91000 r-xp 00000000 08:02 720914 /lib/libgcc_s.so.1
b7f91000-b7f92000 r--p 0000c000 08:02 720914 /lib/libgcc_s.so.1
b7f92000-b7f93000 rw-p 0000d000 08:02 720914 /lib/libgcc_s.so.1
b7f93000-b7f97000 rw-p b7f93000 00:00 0
b7f97000-b7fb1000 r-xp 00000000 08:02 721209 /lib/ld-2.8.90.so
b7fb1000-b7fb2000 r-xp b7fb1000 00:00 0 [vdso]
b7fb2000-b7fb3000 r--p 0001a000 08:02 721209 /lib/ld-2.8.90.so
b7fb3000-b7fb4000 rw-p 0001b000 08:02 721209 /lib/ld-2.8.90.so
...

Read more...

Revision history for this message
Miloš Mandarić (mandzo18) wrote :

I can confirm this bug. Here is little better backtrace:

#0 0xb7fc8430 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7e34880 in raise () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0xb7e36248 in abort () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#3 0xb7e7210d in __libc_message () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#4 0xb7e783f4 in malloc_printerr () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#5 0x08048e66 in main (argc=Cannot access memory at address 0x4bc9
) at input.c:205
 frequency = 2400
 diameter = 0.0625
 d = (double **) 0xa011bd8
 p = (double **) 0xa011c28
 min_f = 2100
 max_f = 2600
 step_f = 50
 angular_step = 15
 elements = 5
 i = <value optimized out>
 fixed_diameter = 1
 parasitic = 4
 c = <value optimized out>
 hflg = 0
 errflg = <value optimized out>
 scale_factor = 39.369999999999997
 response = 121 'y'
 filename = 0xa011008 "/lib/libgcc_s.so.1"
 notes = 0xa0113f8 "test"
 type = 0x804a7c3 "\"\""
 data_entry = 105 'i'
 fp = (FILE *) 0xa011cd0

Changed in yagiuda:
status: New → Confirmed
Revision history for this message
Miloš Mandarić (mandzo18) wrote :

Here is a patch. You may try to build it your self. Here is a tutorial https://wiki.ubuntu.com/UbuntuPackagingGuide/BuildFromDebdiff
I will try latter to upload it to my ppa archive.

Revision history for this message
Miloš Mandarić (mandzo18) wrote :

You can install it now from my ppa archive. Just add these two lines to /etc/apt/sources.list:

deb http://ppa.launchpad.net/mandzo18/ubuntu intrepid main
deb-src http://ppa.launchpad.net/mandzo18/ubuntu intrepid main

and install it with your favorite package manager or do an upgrade if it's currently installed. To upgrade it, do it like this:

sudo apt-get update && sudo apt-get upgrade

Revision history for this message
Miloš Mandarić (mandzo18) wrote :
Revision history for this message
MMarking (cpt-mocha) wrote :

Working great!! Thanks very much!

Revision history for this message
Charlie_Smotherman (cjsmo) wrote :

This bug has been fixed with the 1.19-5 upload to debian. Current ubuntu version 1.19-5 setting bug to fixed released.

Changed in yagiuda:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.