Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » mingw/gdb troubles
mingw/gdb troubles [message #45261] Sun, 25 October 2015 21:36 Go to next message
mirek is currently offline  mirek
Messages: 13990
Registered: November 2005
Ultimate Member
While trying to reestablish mingw coupled releases, I have quite a trouble with gdb - it crashes all the time (with theide or without).

So the question for mingw users: Are you able to use gdb? Is there any fix to the situation?

Mirek
[Solved] Re: mingw/gdb troubles [message #45266 is a reply to message #45261] Mon, 26 October 2015 12:43 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13990
Registered: November 2005
Ultimate Member
Resolved! I had -gstabs in commandline. With -ggdb it works like charm (with refurbished 'legacy' debugger).

[Updated on: Mon, 26 October 2015 12:47]

Report message to a moderator

Re: mingw/gdb troubles [message #45267 is a reply to message #45261] Mon, 26 October 2015 12:50 Go to previous messageGo to next message
omari is currently offline  omari
Messages: 267
Registered: March 2010
Experienced Member
Hi Mirek,

I investigated this probleme, and i found that ide\Debuggers\MIValue is infected by the behavior described in this thread:

How to fix this strong behaviore of MSC compiler & temporary value ?

please, choose the best solution and apply it to MIValue class.



regards
omari.
Re: mingw/gdb troubles [message #45269 is a reply to message #45267] Mon, 26 October 2015 13:57 Go to previous message
mirek is currently offline  mirek
Messages: 13990
Registered: November 2005
Ultimate Member
omari wrote on Mon, 26 October 2015 12:50
Hi Mirek,

I investigated this probleme, and i found that ide\Debuggers\MIValue is infected by the behavior described in this thread:

How to fix this strong behaviore of MSC compiler & temporary value ?

please, choose the best solution and apply it to MIValue class.



Will check, however I am in process of refurbishing the older debugger (which is not using MIValue).

Mirek
Previous Topic: How to fix this strong behaviore of MSC compiler & temporary value ?
Next Topic: Considering different approach to Win32 release
Goto Forum:
  


Current Time: Wed Jul 17 22:25:52 CEST 2024

Total time taken to generate the page: 0.02773 seconds