Re: compile error: pdfreport : font name in output sectrion

Fix verified,

Thanks a lot


On Fri, Oct 3, 2014 at 7:00 AM, Mike Aubury <[email protected]> wrote:
> Should be fixed in CVS now
>
> On 2 October 2014 16:26, Fernando Ortiz <[email protected]> wrote:
>>
>> Just migrated to 1.2-37, it worked fine with 1.2-1
>>
>> If I set the default font name in the output section the compile
>> aborts with segmentation fault
>>
>> $ cat fontpdf.4gl
>> main
>> start report pdftest to "fontpdf.pdf"
>> output to report pdftest()
>> finish report pdftest
>> end main
>>
>> pdfreport pdftest()
>> output
>>    font name "Times-Roman"
>> format
>>    on every row
>>        print "Hello"
>> end report
>>
>> $ 4glc fontpdf.4gl
>> Segmentation fault
>>
>> $ gdb 4glc
>> sGNU gdb (GDB) CentOS (7.0.1-45.el5.centos)
>> ...
>> (gdb) set args fontpdf.4gl
>> (gdb) run
>> Starting program: /opt/aubit4gl/bin/4glc fontpdf.4gl
>> warning: no loadable sections found in added symbol-file
>> system-supplied DSO at 0x2aaaaaaab000
>> [Thread debugging using libthread_db enabled]
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00000037c927877e in strcpy () from /lib64/libc.so.6
>> (gdb) bt
>> #0  0x00000037c927877e in strcpy () from /lib64/libc.so.6
>> #1  0x00002aaaaab05955 in A4GL_strcpy (dest=0x48c98d "\"Helvetica\"",
>>     src=0x7ffffffbc520 "\"Times-Roman\"", f=0x4f1dec "fgl.infx.yacc",
>> l=8534,
>>     sd=8) at corba_server_util.c:270
>> #2  0x000000000046e404 in a4gl_yyparse ()
>> #3  0x000000000047fb67 in FGLPARSE_doparse ()
>> #4  0x0000000000418ded in doparse () at API_parse_self.c:65
>> #5  0x000000000041ba90 in compile_4gl (compile_object=0,
>>     fgl_basename=0x7fffffffe5e0 "fontpdf",
>>     incl_path=0x7fffffffe050 "-I\"/opt/aubit4gl/incl\"
>> -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
>> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
>> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I"...,
>>     silent=0, verbose=0, output_object=0x75aa80 "", win_95_98=0,
>>     informix_esql=0x7ffffffed440 "esql ",
>>     pg_esql=0x7ffffffed3c0 "\"/bin/ecpg\"", extra_ccflags=0x75a580 "",
>>     preserve_warn=0, each_obj_to_so=0, put_object_in_currdir=1,
>>     all_objects=0x19aec90 "") at compile.c:1361
>> #6  0x000000000041a331 in initArguments (argc=2, argv=0x7fffffffe898)
>>     at compile.c:735
>> #7  0x0000000000418b32 in main (argc=2, argv=0x7fffffffe898) at 4glc.c:170
>>
>> Thanks
>>
>>
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Aubit4gl-discuss mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/aubit4gl-discuss
>
>

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk