bugDDD - Bugs: bug #64350, clicking in backtrace causes...

 
 

bug #64350: clicking in backtrace causes display of file above the one selected

Submitter:  None
Submitted:  Mon 26 Jun 2023 05:51:47 PM UTC
   
 
Category:  Source/Code view Severity:  3 - Normal
Item Group:  None Status:  Works For Me
Privacy:  Public Assigned to:  None
Open/Closed:  Closed Release:  3.4.0
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 15 Aug 2023 06:16:32 PM UTC, comment #5: 

Closed:  Not a problem.

Michael Eager <eager>
Group administrator
Tue 15 Aug 2023 05:49:22 PM UTC, comment #4: 

I spent the morning recompiling GDB and managed to get a version which issues no warning message when executed.  Without the gdb warning in the backtrace everything works as it should in DDD.

The problem is not a function of the program being debugged, but of gdb issuing a warning message.  It might be worthwhile to keep gdb warnings from showing up in the backtrace, but if gdb is configured correctly it won't happen anyway.

From my perspective this can be closed.

Anonymous
Tue 15 Aug 2023 04:03:15 PM UTC, comment #3: 

Please upload a test program.   Does your program use Python?

Is GDB stopping at a breakpoint or because of an error?

Please register with Savannah and add your name.




Michael Eager <eager>
Group administrator
Tue 15 Aug 2023 01:59:20 PM UTC, comment #2: 

CentOS 7, gcc-11.2 gdb 8.2

Usually compile with "-g -gdwarf-4 -ggdb --std=c++20"

The same issue was present in ver. 3.12

Backtrace looks something like:

<backtrace>
.........
#2 ......
#1 0x00.....  in FileUtils::uniRead () At FileUtils.cpp:204
#0 SSData::insertDataRow () at SSData.cpp:530
Python Exception <type 'exceptions.ImportError'> itertools.so: undefined symbol:PyExc_StopIteration:
</backtrace>

I suspect that the issue is the Python Exception that is always at the bottom of backtrace, but I have no idea why I get that error.

If I click on the Python exception I get SSData.cpp:530.
If I click on #0 I get FileUtils.cpp:204 ...

I have been working around this for years so it's not that big of a deal.  Unfortunately I have no way of posting a test program, but it always happens.  Once again I suspect the error message is throwing the counting off by one.

BTW I'm really glad this project has been resurrected.

ges

Anonymous
Tue 27 Jun 2023 06:10:52 PM UTC, comment #1: 

When I open the backtrace listing and click on the entries, the correct file and line are displayed. 

Can you upload a test program and describe in more detail what you are doing and what you see?

Michael Eager <eager>
Group administrator
Mon 26 Jun 2023 05:51:47 PM UTC, original submission:  

When navigating a backtrace and examining the code clicking on a row causes the file in the above row to be displayed in the source window.  A minor inconvenience, but annoying none the less

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by eager (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-08-15 eager Open/ClosedOpen Closed
    2023-06-27 eager StatusNone Works For Me

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code