Recent Posts

Pages: 1 ... 8 9 [10]
91
Well, the first thing you have to understand.  We use GDB's MI interface.

There's no guarantee that you'll get the same answer from the equivelent MI command as the GDB CLI command.  Someone could have massaged the CLI command to filter out less relevant registers, and done nothing with the MI implementation (or not documented it).
92
Thanks. 

I could see it being a pain, which is why I suggested a restricted output of just the debug-send-command output and not all the MI output that SE issues and receives for its normal use.

Regardless, I look forward to seeing what gets implemented when it comes.   I'd love to use SE more for my debugging interface as it is excellent with what it does have implemented.  But for now I'll fall back to gdb (or other GUI tools on top of gdb).
93
Click on the "Name" column, you should be able to reverse the sort order.

We just display the registers that GDB gives us.  As far as I know, GDB doesn't have an option to filter that down to the relevant ones per-context.  I could file a feature request to add filtering by name to the Registers dialog.

That is odd as I resorted to using gdb-multiarch on a Linux box to old school debug this issue and it does not show all these extra registers that SE reports. 
94
We have a feature request filed for this one.  It's going to create problems and will be a maintenance nightmare, nobody will like reading the GDB MI output, and people will misuse it and complain that the debugger is left in an untenable state, nevertheless I do recognize that it needs to be done for some future release. 

Believe it or not, despite all this, it is high on our list of priorities, but other things are currently higher.
95
Click on the "Name" column, you should be able to reverse the sort order.

We just display the registers that GDB gives us.  As far as I know, GDB doesn't have an option to filter that down to the relevant ones per-context.  I could file a feature request to add filtering by name to the Registers dialog.
96
SlickEdit® / Re: Debug memory chops address
« Last post by b on August 08, 2018, 04:06:31 pm »
This will be fixed in v23 beta2, and I will also add the fix for the next v22.0.2 hot fix.

Thanks!
97
This topic has been moved to SlickEdit 2018 v23 Beta Discussion as it was accidentally posted to the wrong board.

https://community.slickedit.com/index.php?topic=16272.0
98
Since SlickEdit supports a native GDB, I'm back to using the IDE to debug.  However, I've run into one display issue that is driving me crazy.

It appears that when one has the registers window open, it attempts an enumeration of every possible register, and after single instruction stepping, it resets the window back to the top.  However, the registers of interest are v0 and v1, which are at the bottom.  Is there a way to tell SE not to display registers that are 'Unknown'?
99
Fixed for the next beta drop.
100
SlickEdit® / Re: Debug memory chops address
« Last post by Dennis on August 08, 2018, 02:08:45 pm »
This will be fixed in v23 beta2, and I will also add the fix for the next v22.0.2 hot fix.
Pages: 1 ... 8 9 [10]