Bug 465245

Summary: Tracing does not work
Product: [Fedora] Fedora Reporter: Roberto Bagnara <bagnara>
Component: gprologAssignee: Jochen Schmitt <jochen>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 8CC: bagnara, jochen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-14 15:01:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Roberto Bagnara 2008-10-02 12:32:06 UTC
Description of problem:

Tracing does not work: with the tracer activated even a very
simple goal fails.

Version-Release number of selected component (if applicable):

$ rpm -q gprolog
gprolog-1.3.0-17.fc8

How reproducible:

$ gprolog
GNU Prolog 1.3.0
By Daniel Diaz
Copyright (C) 1999-2007 Daniel Diaz
| ?- trace.
The debugger will first creep -- showing everything (trace)

yes
{trace}
| ?- X=1.

no
{trace}
| ?-

Comment 1 Roberto Bagnara 2008-10-02 12:34:20 UTC
This bug is there since at least Fedora 6.

Comment 2 Jochen Schmitt 2008-10-05 18:44:53 UTC
Thank you, that you have take the time to report this bug. Unfortunately, I could not find a quick solution for your issue. So I have forwarded this issue to the upstream author.

Best Regards:

Jochen Schmitt

Comment 3 Jochen Schmitt 2008-10-12 17:35:30 UTC
Uprsteam wrote that this bug is caused by gcc >= 4 and should be fixed in the upcomming release 1.3.1.