[abrt] crash in rpm-build-4.7.2-1.fc12: fdGetFp: Process /usr/bin/rpmbuild was killed by signal 11 (SIGSEGV)

abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: rpmbuild -bb jboss.spec
component: rpm
crash_function: fdGetFp
executable: /usr/bin/rpmbuild
global_uuid: 3177ee6dd4fd223bc9ee11d26cbb69006628037e
kernel: 2.6.32.12-115.fc12.x86_64
package: rpm-build-4.7.2-1.fc12
rating: 4
reason: Process /usr/bin/rpmbuild was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

comment
-----
The definition of jboss.spec has the following macro (BAD):
BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX}

Should be:
BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX)

Last ")" was bad replaced by "}".

How to reproduce
-----
1. rpmbuild -bb jboss.spec

Created attachment 421635
File: backtrace

Where can I find this particular jboss.spec to reproduce the issue?

(In reply to comment #2)
> Where can I find this particular jboss.spec to reproduce the issue?

The segmentation fault is immediately and happens even before the %prep phase. It happens because the BuildRoot line:

# BAD syntax: Last ")" was bad replaced by "}".
BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX}

# Should be and works fine
BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX)

I think the jboss.spec has a lot of information that I believe isn't important for analysis. However I'll try to create a simpler one just with the sufficient information to generate the crash (I'll post here soon as I can).

Created attachment 421987
the jboss.spec file

Thanks, easily reproduced with that.

As I kinda suspected, there's no "minimal" reproducer for this: the spec parser is looking for the closing parenthesis and overruns the spec linebuffer while doing so (case of a missing bounds check), and this wont happen with the "minimal reproducer" spec sizes.

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.