[Bug 706462] parse: fix build with Bison 3

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=706462
  GStreamer | gstreamer (core) | git

Bruce Dubbs <bruce.dubbs> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bruce.dubbs at gmail.com

--- Comment #5 from Bruce Dubbs <bruce.dubbs at gmail.com> 2013-08-21 13:25:21 UTC ---
I applied the patch and the build completed without error, but running 

gdb ./tools/.libs/gst-launch-1.0

resulted in a segmentation fault:

(gdb) bt
#0  priv_gst_parse_yylex (yylval_param=yylval_param at entry=0x7fffffffd3b0,
yyscanner=0x0)
    at lex.priv_gst_parse_yy.c:1157
#1  0x00007ffff7b86dfa in priv_gst_parse_yyparse (scanner=<optimized out>, 
    graph=graph at entry=0x7fffffffdce0) at grammar.tab.c:1809
#2  0x00007ffff7b88d08 in priv_gst_parse_launch (str=str at entry=0x65bfe0 "", 
    error=error at entry=0x7fffffffde38, ctx=ctx at entry=0x0,
flags=flags at entry=GST_PARSE_FLAG_NONE)
    at ./grammar.y:938
#3  0x00007ffff7b801a5 in gst_parse_launch_full (pipeline_description=0x65bfe0
"", 
    context=context at entry=0x0, flags=flags at entry=GST_PARSE_FLAG_NONE, 
    error=error at entry=0x7fffffffde38) at gstparse.c:324
#4  0x00007ffff7b80405 in gst_parse_launchv_full (argv=argv at entry=0x611ff0, 
    context=context at entry=0x0, flags=flags at entry=GST_PARSE_FLAG_NONE, 
    error=error at entry=0x7fffffffde38) at gstparse.c:262
#5  0x00007ffff7b8050c in gst_parse_launchv (argv=argv at entry=0x611ff0, 
    error=error at entry=0x7fffffffde38) at gstparse.c:215
#6  0x00000000004033fc in main (argc=1, argv=0x7fffffffe1b8) at
gst-launch.c:996


Yes, the command should have some parameters, but not having any should error
out, not segfault.  The same test using Bison 2.7 works properly.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.