Segmentation fault in augtool and augeas.rb

Bug #814569 reported by Ruslan Lutsenko
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
augeas (Ubuntu)
Fix Released
High
Unassigned
Lucid
Won't Fix
High
Unassigned

Bug Description

When run augtool receive Segmentation fault:
# augtool
Segmentation fault

Gdb output:
(gdb) run
Starting program: /usr/bin/augtool
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7b9aa7c in ?? () from /usr/lib/libaugeas.so.0

Puppet output:
/usr/lib/ruby/1.8/puppet/provider/augeas/augeas.rb:139: [BUG] Segmentation fault

System details:

augeas-tools:
  Installed: 0.7.0-1ubuntu1
  Candidate: 0.7.0-1ubuntu1
  Version table:
 *** 0.7.0-1ubuntu1 0
        500 ftp://ua.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Description: Ubuntu 10.04 LTS
Release: 10.04

2.6.32-21-server #32-Ubuntu SMP

Changed in augeas (Ubuntu):
importance: Undecided → High
Revision history for this message
Dave Walker (davewalker) wrote :

I could not reproduce this in oneiric, therefore marking fix released, as it has been at least resolved in the development release. Opening a task for Lucid, needs to be reproduced. Thanks.

Changed in augeas (Ubuntu):
status: New → Fix Released
Changed in augeas (Ubuntu Lucid):
importance: Undecided → High
Revision history for this message
David Caro (dcaro) wrote :

I was able to reproduce this error on centos 6.5, when having a >24 MB /etc/sysconfig/nfs configuration file, any tool using augeas-libs just broke with segmentation fault.

Using augeas-libs-1.0.0-5.el6_5.1.x86_64

Fixed just trimming down the faulty configuration file as a workaround.

Reproduced easily just appending data into the file until it's big enough (17 MB was enough for me). It does not matter if you add real configuration entries or just comments.

This is what I used to test it:
  for i in $(seq 1000000); do echo "#WHATEVER=NOTHIG" >> /etc/sysconfig/nfs; done

After that running augtool:
  # augtool
  Segmentation fault

With gdb:
 # gdb augtool
 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1)
 Copyright (C) 2010 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-redhat-linux-gnu".
 For bug reporting instructions, please see:
 <http://www.gnu.org/software/gdb/bugs/>...
 Reading symbols from /usr/bin/augtool...(no debugging symbols found)...done.
 Missing separate debuginfos, use: debuginfo-install augeas-1.0.0-5.el6_5.1.x86_64
 (gdb) run
 Starting program: /usr/bin/augtool

 Program received signal SIGSEGV, Segmentation fault.
 0x00007ffff7bbe2a1 in ?? () from /usr/lib64/libaugeas.so.0
 (gdb)

And attached an strace of the run (don't get scared by the strange config files please :) ).

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in augeas (Ubuntu Lucid):
status: New → Confirmed
Revision history for this message
David Caro (dcaro) wrote :

Opened an issue about it on main augeas bug tracker (github) as it's not Ubuntu specific.

https://github.com/hercules-team/augeas/issues/120

Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in augeas (Ubuntu Lucid):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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