internal dbg, snapshot 20000101-A

jbb jbb at ihug.co.nz
Tue Jan 4 18:11:23 GMT 2000


On Wed, 05 Jan 2000, you wrote:

> I did! Jan 04 1999, 11.?? 

10.?? GMT?
That's got everything then.

> It compiled flawlessly, but if I try to debug, 
> the program exits without even reaching the first line of code.
> Running it from kdevelop works.
> there are no debug messages in the console.
> 
> My system:
> 	SuSE 6.3,
> 	egcs 2.91.66
> 	kde 1.1.2
> 	qt 1.44
> 	gdb 4.18
> Is there a chance to get the debugger code to output some more information to
> the console?

Yes, to more output - No, to console output

I have two compile flags 
-DGDB_MONITOR - in/out of gdb messages
-DDBG_MONITOR - the above plus internal debug messages

Recompile with one of these flags (I suggest -DGDB_MONITOR) and you'll get
another output tab "debugger". You can cut and paste from this window.

Also when you recompile can you add debug symbols to kdevelop (--enable-debug
is the configure switch needed)

This ones a mystery to me, so I'm going to need your help.

Just a thought: does your program need any arguments to run? I was using the
"program arguments" but now have separate arguments for when you run
in the debugger.

-- 
Regards,

jbb
http://homepages.ihug.co.nz/~jbb




More information about the KDevelop mailing list