User forums > Nightly builds

The 11 february 2007 build is out.

<< < (2/4) > >>

indigo0086:
Yes, go to debug->debugging windows->Dissassembly

To address a fix request.
There's still a problem with the "export->As RTF..." function.  It doesn't output anything after an escape character '\' up until a delimiter like ' " or ' '.  For example


--- Code: ---while(*end != '\"')
//and
cout << "\"Hello" << world  << "\""<< endl;

--- End code ---

becomes

--- Code: ---while(*end != '')
//and
cout << "Hello" << world  << ""<< endl;

--- End code ---

it works for the other two formats, but rtf is more formattable.

Marenz:
@ Silverling: When you debug your application, then you can also disassembler it, at least here under linux it works. just press the "Next Instruction" Button.

--Ano

Silverling:

--- Quote from: indigo0086 on February 12, 2007, 04:26:13 pm ---debug->debugging windows->Dissassembly

--- End quote ---


--- Quote from: Suprano on February 12, 2007, 04:26:13 pm ---@ Silverling: When you debug your application, then you can also disassembler it, at least here under linux it works. just press the "Next Instruction" Button.

--Ano

--- End quote ---

Thanks, and sorry. I didn't notice because I had de-activated the debug plugin and didn't bother going to the "debug" menu.
Now I start the debugging session (Start F8) and windbg claims that some options are invalid (nx, fullname, quiet by that order) :( One more thing: does the disassembler allow me to edit the ASM code?

Lastly, I'm coding in D, using DMD.

ir0nk0ala:
I may have found a bug:
I started debugging a small project (one file) with one breakpoint, but when i tried to stop, C::B didn't respond. I tried continuing, going to the next line, etc., but nothing worked. I finally closed the project, the debugger terminated, and now C::B is locked up. I'm running C::B under Ubuntu 6.10, rev 3592, GNU gdb 6.4.90-debian. I'm not sure if this is a bug or just a mistake of my own  :(. Any ideas?

UPDATE:
When I ended the frozen C::B process and started it back up, it gave me the message "Deleted stale lock file" and told me the location. Relevant..?

Pecan:

--- Quote from: ir0nk0ala on February 12, 2007, 11:02:27 pm ---I may have found a bug:
I started debugging a small project (one file) with one breakpoint, but when i tried to stop, C::B didn't respond. I tried continuing, going to the next line, etc., but nothing worked. I finally closed the project, the debugger terminated, and now C::B is locked up. I'm running C::B under Ubuntu 6.10, rev 3592, GNU gdb 6.4.90-debian. I'm not sure if this is a bug or just a mistake of my own  :(. Any ideas?

--- End quote ---

Bug. It happens to me 10-15 times a day. I'm trying to trace some of 'em down.
Open a terminal. Do a ps x, then killall for the program you were debugging, then killall codeblocks.

Navigation

[0] Message Index

[#] Next page

[*] Previous page