Forum Topic - Momentix IDE Debugger Error:
   
Momentix IDE Debugger Error  
Greetings,

the Momentix/Eclipse IDE Debugger (maybe the used debugger is the reason, I am not sure here) messes up things 
completely when debugging QNX-Accplications with classes including static member pointers. After having initialized them
, when using "step in"or step over" debugging methods, the heap seems to be destroyed and return points, function 
boundaries etc. are  becoming invalid.

Attached file demonstrates the behaviour. How to reproduce: Start debugging an application, and press F6 or F5 or set a 
breakpoint at the point of the pointer initialization and afterwards use step in/over. Using F8 until the debugger 
reaches the entry point (main here) works around the bug. 

Best regards,
Andy

Attachment: Text momentixDebuggerBug.cpp 416 bytes
Re: Momentix IDE Debugger Error  
Which architecture, release and gdb version are you using?


Works for me on x86, 6.5.0, gdb 6.8 rev. 506 :



(gdb) b 21
Breakpoint 1 at 0x8048757: file 
/home/aristovski/testcases/forumproblem/main.cc, line 21.
(gdb) c
The program is not being run.
(gdb) r
Starting program: /shared/forumproblem_g
[New pid 225310 tid 1]

Breakpoint 1, __static_initialization_and_destruction_0 (__initialize_p=1,
     __priority=65535) at /home/aristovski/testcases/forumproblem/main.cc:21
21      int* testDebug::devastator = new int[666];
(gdb) step
32      }
(gdb)
0x080487c2 in __do_global_ctors_aux ()
(gdb)
Single stepping until exit from function __do_global_ctors_aux,
which has no line number information.
0x0804848e in _init ()
(gdb)
Single stepping until exit from function _init,
which has no line number information.
0x080485c9 in _start ()
(gdb)
Single stepping until exit from function _start,
which has no line number information.
0xb0367750 in _init_array () from /opt/qnx650/target/qnx6/x86/lib/libc.so.3
(gdb)
Single stepping until exit from function _init_array,
which has no line number information.
0x080485d8 in _start ()
(gdb)
Single stepping until exit from function _start,
which has no line number information.
main (argc=0x1, argv=134512356)
     at /home/aristovski/testcases/forumproblem/main.cc:24
24      {
(gdb)
26              int j=0;
(gdb)
27              for (int i=0; i < 9; ++i)
(gdb)
29                      j+=i;
(gdb)
27              for (int i=0; i < 9; ++i)

(gdb) show version
GNU gdb 6.8 qnx-nto (rev. 506)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu 
--target=i486-pc-nto-qnx6.5.0".


On 07/19/2011 07:47 AM, Andreas Beschorner wrote:
> Greetings,
>
> the Momentix/Eclipse IDE Debugger (maybe the used debugger is the
> reason, I am not sure here) messes up things completely when debugging
> QNX-Accplications with classes including static member pointers. After
> having initialized them, when using "step in"or step over" debugging
> methods, the heap seems to be destroyed and return points, function
> boundaries etc. are becoming invalid.
>
> Attached file demonstrates the behaviour. How to reproduce: Start
> debugging an application, and press F6 or F5 or set a breakpoint at the
> point of the pointer initialization and afterwards use step in/over.
> Using F8 until the debugger reaches the entry point (main here) works
> around the bug.
>
> Best regards,
> Andy
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post87420
>
AW: Momentix IDE Debugger Error  
Greetings mate,

how can I get information about which gdb version is used within the toolchain?
As gdb is not installed on the virtual machine/ target I need to do this via the IDE somehow...

The system itself: X86 running QNX on a virtual machine in Windows 7 64bit, Momentix 6.5.0.

Thanks for help,
Andreas

-----Ursprüngliche Nachricht-----
Von: Aleksandar Ristovski [mailto:community-noreply@qnx.com] 
Gesendet: Dienstag, 19. Juli 2011 15:17
An: general-ide
Betreff: Re: Momentix IDE Debugger Error

Which architecture, release and gdb version are you using?


Works for me on x86, 6.5.0, gdb 6.8 rev. 506 :



(gdb) b 21
Breakpoint 1 at 0x8048757: file 
/home/aristovski/testcases/forumproblem/main.cc, line 21.
(gdb) c
The program is not being run.
(gdb) r
Starting program: /shared/forumproblem_g
[New pid 225310 tid 1]

Breakpoint 1, __static_initialization_and_destruction_0 (__initialize_p=1,
     __priority=65535) at /home/aristovski/testcases/forumproblem/main.cc:21
21      int* testDebug::devastator = new int[666];
(gdb) step
32      }
(gdb)
0x080487c2 in __do_global_ctors_aux ()
(gdb)
Single stepping until exit from function __do_global_ctors_aux,
which has no line number information.
0x0804848e in _init ()
(gdb)
Single stepping until exit from function _init,
which has no line number information.
0x080485c9 in _start ()
(gdb)
Single stepping until exit from function _start,
which has no line number information.
0xb0367750 in _init_array () from /opt/qnx650/target/qnx6/x86/lib/libc.so.3
(gdb)
Single stepping until exit from function _init_array,
which has no line number information.
0x080485d8 in _start ()
(gdb)
Single stepping until exit from function _start,
which has no line number information.
main (argc=0x1, argv=134512356)
     at /home/aristovski/testcases/forumproblem/main.cc:24
24      {
(gdb)
26              int j=0;
(gdb)
27              for (int i=0; i < 9; ++i)
(gdb)
29                      j+=i;
(gdb)
27              for (int i=0; i < 9; ++i)

(gdb) show version
GNU gdb 6.8 qnx-nto (rev. 506)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu 
--target=i486-pc-nto-qnx6.5.0".


On 07/19/2011 07:47 AM, Andreas Beschorner wrote:
> Greetings,
>
> the Momentix/Eclipse IDE Debugger (maybe the used debugger is the
> reason, I am not sure here) messes up things completely when debugging
> QNX-Accplications with classes including static member pointers. After
> having initialized them, when using "step in"or step over" debugging
> methods, the heap seems to be destroyed and return points, function
> boundaries etc. are becoming invalid.
>
> Attached file demonstrates the behaviour. How to reproduce: Start
> debugging an application, and press F6 or F5 or set a breakpoint at the
> point of the pointer initialization and afterwards use step in/over.
> Using F8 until the debugger reaches the entry point (main here) works
> around the bug.
>
> Best regards,
> Andy
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post87420
>




_______________________________________________

General
http://community.qnx.com/sf/go/post87421


-- 
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
Re: AW: Momentix IDE Debugger Error  
In your IDE, debug perspective, click on the gdb entry in the left-hand 
side view where thread, inferior, is shown in a tree. Bottom view should 
then show gdb console. In it, type:

show version

it will print the version.

Another way is to open your 'cmd.exe' and type:

C:> ntox86-gdb
(gdb) show version


Could you turn on verbose logging in the IDE, in your debug 
configuration, Debugger tab, scroll down and check the checkbox. Then 
copy the output from gdb console and paste it here (or in an attached file).







On 07/19/2011 09:25 AM, Andreas Beschorner wrote:
> Greetings mate,
>
> how can I get information about which gdb version is used within the toolchain?
> As gdb is not installed on the virtual machine/ target I need to do this via the IDE somehow...
>
> The system itself: X86 running QNX on a virtual machine in Windows 7 64bit, Momentix 6.5.0.
>
> Thanks for help,
> Andreas
>
> -----Ursprüngliche Nachricht-----
> Von: Aleksandar Ristovski [mailto:community-noreply@qnx.com]
> Gesendet: Dienstag, 19. Juli 2011 15:17
> An: general-ide
> Betreff: Re: Momentix IDE Debugger Error
>
> Which architecture, release and gdb version are you using?
>
>
> Works for me on x86, 6.5.0, gdb 6.8 rev. 506 :
>
>
>
> (gdb) b 21
> Breakpoint 1 at 0x8048757: file
> /home/aristovski/testcases/forumproblem/main.cc, line 21.
> (gdb) c
> The program is not being run.
> (gdb) r
> Starting program: /shared/forumproblem_g
> [New pid 225310 tid 1]
>
> Breakpoint 1, __static_initialization_and_destruction_0 (__initialize_p=1,
>       __priority=65535) at /home/aristovski/testcases/forumproblem/main.cc:21
> 21      int* testDebug::devastator = new int[666];
> (gdb) step
> 32      }
> (gdb)
> 0x080487c2 in __do_global_ctors_aux ()
> (gdb)
> Single stepping until exit from function __do_global_ctors_aux,
> which has no line number information.
> 0x0804848e in _init ()
> (gdb)
> Single stepping until exit from function _init,
> which has no line number information.
> 0x080485c9 in _start ()
> (gdb)
> Single stepping until exit from function _start,
> which has no line number information.
> 0xb0367750 in _init_array () from /opt/qnx650/target/qnx6/x86/lib/libc.so.3
> (gdb)
> Single stepping until exit from function _init_array,
> which has no line number information.
> 0x080485d8 in _start ()
> (gdb)
> Single stepping until exit from function _start,
> which has no line number information.
> main (argc=0x1, argv=134512356)
>       at /home/aristovski/testcases/forumproblem/main.cc:24
> 24      {
> (gdb)
> 26              int j=0;
> (gdb)
> 27              for (int i=0; i<  9; ++i)
> (gdb)
> 29                      j+=i;
> (gdb)
> 27              for (int i=0; i<  9; ++i)
>
> (gdb) show version
> GNU gdb 6.8 qnx-nto (rev. 506)
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>;
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "--host=i686-pc-linux-gnu
> --target=i486-pc-nto-qnx6.5.0".
>
>
> On 07/19/2011 07:47 AM, Andreas Beschorner wrote:
>> Greetings,
>>
>> the Momentix/Eclipse IDE Debugger (maybe the used debugger is the
>> reason, I am not sure here) messes up things completely when debugging
>> QNX-Accplications with classes including static member pointers. After
>> having initialized them, when using "step in"or step over" debugging
>> methods, the heap seems to be destroyed and return...
View Full Message
AW: Momentix IDE Debugger Error  
Hi again,

gdb 6.8, rev. 506 here, too


-----Ursprüngliche Nachricht-----
Von: Aleksandar Ristovski [mailto:community-noreply@qnx.com] 
Gesendet: Dienstag, 19. Juli 2011 15:17
An: general-ide
Betreff: Re: Momentix IDE Debugger Error

Which architecture, release and gdb version are you using?


Works for me on x86, 6.5.0, gdb 6.8 rev. 506 :



(gdb) b 21
Breakpoint 1 at 0x8048757: file 
/home/aristovski/testcases/forumproblem/main.cc, line 21.
(gdb) c
The program is not being run.
(gdb) r
Starting program: /shared/forumproblem_g
[New pid 225310 tid 1]

Breakpoint 1, __static_initialization_and_destruction_0 (__initialize_p=1,
     __priority=65535) at /home/aristovski/testcases/forumproblem/main.cc:21
21      int* testDebug::devastator = new int[666];
(gdb) step
32      }
(gdb)
0x080487c2 in __do_global_ctors_aux ()
(gdb)
Single stepping until exit from function __do_global_ctors_aux,
which has no line number information.
0x0804848e in _init ()
(gdb)
Single stepping until exit from function _init,
which has no line number information.
0x080485c9 in _start ()
(gdb)
Single stepping until exit from function _start,
which has no line number information.
0xb0367750 in _init_array () from /opt/qnx650/target/qnx6/x86/lib/libc.so.3
(gdb)
Single stepping until exit from function _init_array,
which has no line number information.
0x080485d8 in _start ()
(gdb)
Single stepping until exit from function _start,
which has no line number information.
main (argc=0x1, argv=134512356)
     at /home/aristovski/testcases/forumproblem/main.cc:24
24      {
(gdb)
26              int j=0;
(gdb)
27              for (int i=0; i < 9; ++i)
(gdb)
29                      j+=i;
(gdb)
27              for (int i=0; i < 9; ++i)

(gdb) show version
GNU gdb 6.8 qnx-nto (rev. 506)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu 
--target=i486-pc-nto-qnx6.5.0".


On 07/19/2011 07:47 AM, Andreas Beschorner wrote:
> Greetings,
>
> the Momentix/Eclipse IDE Debugger (maybe the used debugger is the
> reason, I am not sure here) messes up things completely when debugging
> QNX-Accplications with classes including static member pointers. After
> having initialized them, when using "step in"or step over" debugging
> methods, the heap seems to be destroyed and return points, function
> boundaries etc. are becoming invalid.
>
> Attached file demonstrates the behaviour. How to reproduce: Start
> debugging an application, and press F6 or F5 or set a breakpoint at the
> point of the pointer initialization and afterwards use step in/over.
> Using F8 until the debugger reaches the entry point (main here) works
> around the bug.
>
> Best regards,
> Andy
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post87420
>




_______________________________________________

General
http://community.qnx.com/sf/go/post87421


-- 
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
AW: Momentix IDE Debugger Error  
And greetings again,

a colleague of mine hast the same problem as I have. Are you sure you debugged starting F11 and then using F6 and not F8
 or so?

I am having really a lot of problems with the IDE at the moment. Crashes a lot when debugging whereas the executables 
run fine, mudflap shows lots of out of bound errors, when profiling function calls running a program for about 4 minutes
 I get functions using 1900s or more -- you name it...

Best regards,
Andy


-----Ursprüngliche Nachricht-----
Von: Aleksandar Ristovski [mailto:community-noreply@qnx.com] 
Gesendet: Dienstag, 19. Juli 2011 15:17
An: general-ide
Betreff: Re: Momentix IDE Debugger Error

Which architecture, release and gdb version are you using?


Works for me on x86, 6.5.0, gdb 6.8 rev. 506 :



(gdb) b 21
Breakpoint 1 at 0x8048757: file 
/home/aristovski/testcases/forumproblem/main.cc, line 21.
(gdb) c
The program is not being run.
(gdb) r
Starting program: /shared/forumproblem_g
[New pid 225310 tid 1]

Breakpoint 1, __static_initialization_and_destruction_0 (__initialize_p=1,
     __priority=65535) at /home/aristovski/testcases/forumproblem/main.cc:21
21      int* testDebug::devastator = new int[666];
(gdb) step
32      }
(gdb)
0x080487c2 in __do_global_ctors_aux ()
(gdb)
Single stepping until exit from function __do_global_ctors_aux,
which has no line number information.
0x0804848e in _init ()
(gdb)
Single stepping until exit from function _init,
which has no line number information.
0x080485c9 in _start ()
(gdb)
Single stepping until exit from function _start,
which has no line number information.
0xb0367750 in _init_array () from /opt/qnx650/target/qnx6/x86/lib/libc.so.3
(gdb)
Single stepping until exit from function _init_array,
which has no line number information.
0x080485d8 in _start ()
(gdb)
Single stepping until exit from function _start,
which has no line number information.
main (argc=0x1, argv=134512356)
     at /home/aristovski/testcases/forumproblem/main.cc:24
24      {
(gdb)
26              int j=0;
(gdb)
27              for (int i=0; i < 9; ++i)
(gdb)
29                      j+=i;
(gdb)
27              for (int i=0; i < 9; ++i)

(gdb) show version
GNU gdb 6.8 qnx-nto (rev. 506)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu 
--target=i486-pc-nto-qnx6.5.0".


On 07/19/2011 07:47 AM, Andreas Beschorner wrote:
> Greetings,
>
> the Momentix/Eclipse IDE Debugger (maybe the used debugger is the
> reason, I am not sure here) messes up things completely when debugging
> QNX-Accplications with classes including static member pointers. After
> having initialized them, when using "step in"or step over" debugging
> methods, the heap seems to be destroyed and return points, function
> boundaries etc. are becoming invalid.
>
> Attached file demonstrates the behaviour. How to reproduce: Start
> debugging an application, and press F6 or F5 or set a breakpoint at the
> point of the pointer initialization and afterwards use step in/over.
> Using F8 until the debugger reaches the entry point (main here) works
> around the bug.
>
> Best regards,
> Andy
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post87420
>




_______________________________________________

General
http://community.qnx.com/sf/go/post87421


-- 
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
Re: AW: Momentix IDE Debugger Error  
I used gdb from command line.

For diagnosing IDE/gdb interaction, please capture verbose gdb log so we 
can take a look.



On 07/19/2011 09:45 AM, Andreas Beschorner wrote:
> And greetings again,
>
> a colleague of mine hast the same problem as I have. Are you sure you debugged starting F11 and then using F6 and not 
F8 or so?
>
> I am having really a lot of problems with the IDE at the moment. Crashes a lot when debugging whereas the executables 
run fine, mudflap shows lots of out of bound errors, when profiling function calls running a program for about 4 minutes
 I get functions using 1900s or more -- you name it...
>
> Best regards,
> Andy
>
>
> -----Ursprüngliche Nachricht-----
> Von: Aleksandar Ristovski [mailto:community-noreply@qnx.com]
> Gesendet: Dienstag, 19. Juli 2011 15:17
> An: general-ide
> Betreff: Re: Momentix IDE Debugger Error
>
> Which architecture, release and gdb version are you using?
>
>
> Works for me on x86, 6.5.0, gdb 6.8 rev. 506 :
>
>
>
> (gdb) b 21
> Breakpoint 1 at 0x8048757: file
> /home/aristovski/testcases/forumproblem/main.cc, line 21.
> (gdb) c
> The program is not being run.
> (gdb) r
> Starting program: /shared/forumproblem_g
> [New pid 225310 tid 1]
>
> Breakpoint 1, __static_initialization_and_destruction_0 (__initialize_p=1,
>       __priority=65535) at /home/aristovski/testcases/forumproblem/main.cc:21
> 21      int* testDebug::devastator = new int[666];
> (gdb) step
> 32      }
> (gdb)
> 0x080487c2 in __do_global_ctors_aux ()
> (gdb)
> Single stepping until exit from function __do_global_ctors_aux,
> which has no line number information.
> 0x0804848e in _init ()
> (gdb)
> Single stepping until exit from function _init,
> which has no line number information.
> 0x080485c9 in _start ()
> (gdb)
> Single stepping until exit from function _start,
> which has no line number information.
> 0xb0367750 in _init_array () from /opt/qnx650/target/qnx6/x86/lib/libc.so.3
> (gdb)
> Single stepping until exit from function _init_array,
> which has no line number information.
> 0x080485d8 in _start ()
> (gdb)
> Single stepping until exit from function _start,
> which has no line number information.
> main (argc=0x1, argv=134512356)
>       at /home/aristovski/testcases/forumproblem/main.cc:24
> 24      {
> (gdb)
> 26              int j=0;
> (gdb)
> 27              for (int i=0; i<  9; ++i)
> (gdb)
> 29                      j+=i;
> (gdb)
> 27              for (int i=0; i<  9; ++i)
>
> (gdb) show version
> GNU gdb 6.8 qnx-nto (rev. 506)
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>;
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "--host=i686-pc-linux-gnu
> --target=i486-pc-nto-qnx6.5.0".
>
>
> On 07/19/2011 07:47 AM, Andreas Beschorner wrote:
>> Greetings,
>>
>> the Momentix/Eclipse IDE Debugger (maybe the used debugger is the
>> reason, I am not sure here) messes up things completely when debugging
>> QNX-Accplications with classes including static member pointers. After
>> having initialized them, when using "step in"or step over" debugging
>> methods, the heap seems to be destroyed and return points, function
>> boundaries etc. are becoming invalid.
>>
>> Attached file demonstrates the behaviour. How to reproduce: Start
>> debugging an application, and press F6 or F5 or set a breakpoint at the
>> point of the pointer...
View Full Message
Re: AW: Momentix IDE Debugger Error  
Crashes a lot when debugging - could be a problem with app itself which only manifests when debugging, this happens a 
lot - memory layout and contents is
diffrent when app has debug symbols. For debugging make sure your library and binaries exactly the same on host & target - library mismatch can cause this behavior.
Mudflap known to have lots of false positives. Try memory analysis instead.

On 07/19/2011 09:45 AM, Andreas Beschorner wrote:
> And 
greetings again,
> 
> a colleague of mine hast the same problem as I have. Are you sure you debugged starting F11 and then using F6 and not 
F8 or so?
> 
> I am having really a lot of problems with the IDE at the moment. Crashes a lot when debugging whereas the executables 
run fine, mudflap shows lots of out of bound errors, when profiling function calls running a program for about 4 minutes
 I get functions using 1900s or more -- you name it...
> 
> Best regards,
> Andy
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Aleksandar Ristovski [mailto:community-noreply@qnx.com] 
> Gesendet: Dienstag, 19. Juli 2011 15:17
> An: general-ide
> Betreff: Re: Momentix IDE Debugger Error
> 
> Which architecture, release and gdb version are you using?
> 
> 
> Works for me on x86, 6.5.0, gdb 6.8 rev. 506 :
> 
> 
> 
> (gdb) b 21
> Breakpoint 1 at 0x8048757: file 
> /home/aristovski/testcases/forumproblem/main.cc, line 21.
> (gdb) c
> The program is not being run.
> (gdb) r
> Starting program: /shared/forumproblem_g
> [New pid 225310 tid 1]
> 
> Breakpoint 1, __static_initialization_and_destruction_0 (__initialize_p=1,
>      __priority=65535) at /home/aristovski/testcases/forumproblem/main.cc:21
> 21      int* testDebug::devastator = new int[666];
> (gdb) step
> 32      }
> (gdb)
> 0x080487c2 in __do_global_ctors_aux ()
> (gdb)
> Single stepping until exit from function __do_global_ctors_aux,
> which has no line number information.
> 0x0804848e in _init ()
> (gdb)
> Single stepping until exit from function _init,
> which has no line number information.
> 0x080485c9 in _start ()
> (gdb)
> Single stepping until exit from function _start,
> which has no line number information.
> 0xb0367750 in _init_array () from /opt/qnx650/target/qnx6/x86/lib/libc.so.3
> (gdb)
> Single stepping until exit from function _init_array,
> which has no line number information.
> 0x080485d8 in _start ()
> (gdb)
> Single stepping until exit from function _start,
> which has no line number information.
> main (argc=0x1, argv=134512356)
>      at /home/aristovski/testcases/forumproblem/main.cc:24
> 24      {
> (gdb)
> 26              int j=0;
> (gdb)
> 27              for (int i=0; i < 9; ++i)
> (gdb)
> 29                      j+=i;
> (gdb)
> 27              for (int i=0; i < 9; ++i)
> 
> (gdb) show version
> GNU gdb 6.8 qnx-nto (rev. 506)
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> <http://gnu.org/licenses/gpl.html>;
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "--host=i686-pc-linux-gnu 
> --target=i486-pc-nto-qnx6.5.0".
> 
> 
> On 07/19/2011 07:47 AM, Andreas Beschorner wrote:
>> Greetings,
>>
>> the Momentix/Eclipse IDE Debugger (maybe the used debugger is the
>> reason, I am not sure here) messes up things completely when debugging
>> QNX-Accplications with classes including static member pointers. After
>> having initialized them, when using "step in"or step over" debugging
>> methods, the heap seems to be destroyed...
View Full Message
Re: AW: Momentix IDE Debugger Error  
Greetings Elena and Aleksandar,

@Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library confusion
. For large programs, your advice or different or unwanted behaviour is true, but the small program attached should 
really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can do.

@Aleksandar: Find attached a zip-file with 5 images debugXX.png,
01) Starting the debugger and stopping at the  breakpoint where the reference is created
02 .. 04) After pressing F6 once each time
0x) Several F6 presses later

I also included the disassembly which shows that basically indirect addresses seem ok....

Best regards and thanks in advance for help,
Andreas
Attachment: Compressed file debug.zip 337.26 KB
Re: AW: Momentix IDE Debugger Error  
Debug and Release are in different directories on target or on host? How do you launch? Do you upload binary and all 
libraries every time?

On 07/19/2011 10:51 AM, Andreas Beschorner wrote:
> Greetings Elena and Aleksandar,
> 
> @Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library 
confusion. For large programs, your advice or different or unwanted behaviour is true, but the small program attached 
should really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can do.
> 
> @Aleksandar: Find attached a zip-file with 5 images debugXX.png,
> 01) Starting the debugger and stopping at the  breakpoint where the reference is created
> 02 .. 04) After pressing F6 once each time
> 0x) Several F6 presses later
> 
> I also included the disassembly which shows that basically indirect addresses seem ok....
> 
> Best regards and thanks in advance for help,
> Andreas
> 
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post87431
AW: AW: Momentix IDE Debugger Error  
Hoi,

yes, I either upload or drag&drop them manually and execute them on the target. When testing, nothing can be too save!


-----Ursprüngliche Nachricht-----
Von: Elena Laskavaia [mailto:community-noreply@qnx.com] 
Gesendet: Dienstag, 19. Juli 2011 16:59
An: general-ide
Betreff: Re: AW: Momentix IDE Debugger Error

Debug and Release are in different directories on target or on host? How do you launch? Do you upload binary and all libraries every time?

On 07/19/2011 10:51 AM, Andreas Beschorner wrote:
> Greetings Elena and Aleksandar,
> 
> @Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library 
confusion. For large programs, your advice or different or unwanted behaviour is true, but the small program attached 
should really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can do.
> 
> @Aleksandar: Find attached a zip-file with 5 images debugXX.png,
> 01) Starting the debugger and stopping at the  breakpoint where the reference is created
> 02 .. 04) After pressing F6 once each time
> 0x) Several F6 presses later
> 
> I also included the disassembly which shows that basically indirect addresses seem ok....
> 
> Best regards and thanks in advance for help,
> Andreas
> 
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post87431



_______________________________________________

General
http://community.qnx.com/sf/go/post87432


-- 
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
Re: AW: AW: Momentix IDE Debugger Error  
I just tried your example with the IDE and it worked for me without 
issues. (used step after hitting the breakpoint).

Can you provide more details:
- complete build log of your project,
- verbose debug output from gdb: turn on verbose debug output in your 
debug configuration, "Debugger" tab, check "Verbose console mode".


Thanks,

Aleksandar

On 07/19/2011 11:01 AM, Andreas Beschorner wrote:
> Hoi,
>
> yes, I either upload or drag&drop them manually and execute them on the target. When testing, nothing can be too save!
>
>
> -----Ursprüngliche Nachricht-----
> Von: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Gesendet: Dienstag, 19. Juli 2011 16:59
> An: general-ide
> Betreff: Re: AW: Momentix IDE Debugger Error
>
> Debug and Release are in different directories on target or on host? How do you launch? Do you upload binary and all 
libraries every time?
>
> On 07/19/2011 10:51 AM, Andreas Beschorner wrote:
>> Greetings Elena and Aleksandar,
>>
>> @Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library 
confusion. For large programs, your advice or different or unwanted behaviour is true, but the small program attached 
should really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can do.
>>
>> @Aleksandar: Find attached a zip-file with 5 images debugXX.png,
>> 01) Starting the debugger and stopping at the  breakpoint where the reference is created
>> 02 .. 04) After pressing F6 once each time
>> 0x) Several F6 presses later
>>
>> I also included the disassembly which shows that basically indirect addresses seem ok....
>>
>> Best regards and thanks in advance for help,
>> Andreas
>>
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post87431
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post87432
>
>
Re: AW: AW: Momentix IDE Debugger Error  
Try using qnx launch configurations which upload binary for you (and related library if you have custom libraries)
Also check the console for errors especially for mismatches.

On 07/19/2011 11:01 AM, Andreas Beschorner wrote:
> Hoi,
> 
> yes, I either upload or drag&drop them manually and execute them on the target. When testing, nothing can be too save!
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Elena Laskavaia [mailto:community-noreply@qnx.com] 
> Gesendet: Dienstag, 19. Juli 2011 16:59
> An: general-ide
> Betreff: Re: AW: Momentix IDE Debugger Error
> 
> Debug and Release are in different directories on target or on host? How do you launch? Do you upload binary and all 
libraries every time?
> 
> On 07/19/2011 10:51 AM, Andreas Beschorner wrote:
>> Greetings Elena and Aleksandar,
>>
>> @Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library 
confusion. For large programs, your advice or different or unwanted behaviour is true, but the small program attached 
should really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can do.
>>
>> @Aleksandar: Find attached a zip-file with 5 images debugXX.png,
>> 01) Starting the debugger and stopping at the  breakpoint where the reference is created
>> 02 .. 04) After pressing F6 once each time
>> 0x) Several F6 presses later
>>
>> I also included the disassembly which shows that basically indirect addresses seem ok....
>>
>> Best regards and thanks in advance for help,
>> Andreas
>>
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post87431
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post87432
> 
> 
RE: AW: AW: Momentix IDE Debugger Error  
I wrote a script using samba client copy commands which connects to the windows platform and copies all necessary 
libraries and executables, so I do not need to start any launch configuration and thus do not run into problems when 
several apps access the same libs, which often leads to "already in use" conflicts.
And all checks are done: Nothing missing and no incorrect libraries involved.

Regards,
A.

________________________________________
From: Elena Laskavaia [community-noreply@qnx.com]
Sent: Tuesday, July 19, 2011 5:11 PM
To: general-ide
Subject: Re: AW: AW: Momentix IDE Debugger Error

Try using qnx launch configurations which upload binary for you (and related library if you have custom libraries)
Also check the console for errors especially for mismatches.

On 07/19/2011 11:01 AM, Andreas Beschorner wrote:
> Hoi,
>
> yes, I either upload or drag&drop them manually and execute them on the target. When testing, nothing can be too save!
>
>
> -----Ursprüngliche Nachricht-----
> Von: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Gesendet: Dienstag, 19. Juli 2011 16:59
> An: general-ide
> Betreff: Re: AW: Momentix IDE Debugger Error
>
> Debug and Release are in different directories on target or on host? How do you launch? Do you upload binary and all 
libraries every time?
>
> On 07/19/2011 10:51 AM, Andreas Beschorner wrote:
>> Greetings Elena and Aleksandar,
>>
>> @Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library 
confusion. For large programs, your advice or different or unwanted behaviour is true, but the small program attached 
should really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can do.
>>
>> @Aleksandar: Find attached a zip-file with 5 images debugXX.png,
>> 01) Starting the debugger and stopping at the  breakpoint where the reference is created
>> 02 .. 04) After pressing F6 once each time
>> 0x) Several F6 presses later
>>
>> I also included the disassembly which shows that basically indirect addresses seem ok....
>>
>> Best regards and thanks in advance for help,
>> Andreas
>>
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post87431
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post87432
>
>



_______________________________________________

General
http://community.qnx.com/sf/go/post87435

--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.

Re: AW: AW: Momentix IDE Debugger Error  
If you not using proper way of debugging I cannot really help you.

On 07/19/2011 01:51 PM, Andreas Beschorner wrote:
> I wrote a script using samba client copy commands which connects to the windows platform and copies all necessary 
libraries and executables, so I do not need to start any launch configuration and thus do not run into problems when 
several apps access the same libs, which often leads to "already in use" conflicts.
> And all checks are done: Nothing missing and no incorrect libraries involved.
> 
> Regards,
> A.
> 
> ________________________________________
> From: Elena Laskavaia [community-noreply@qnx.com]
> Sent: Tuesday, July 19, 2011 5:11 PM
> To: general-ide
> Subject: Re: AW: AW: Momentix IDE Debugger Error
> 
> Try using qnx launch configurations which upload binary for you (and related library if you have custom libraries)
> Also check the console for errors especially for mismatches.
> 
> On 07/19/2011 11:01 AM, Andreas Beschorner wrote:
>> Hoi,
>>
>> yes, I either upload or drag&drop them manually and execute them on the target. When testing, nothing can be too save!
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Elena Laskavaia [mailto:community-noreply@qnx.com]
>> Gesendet: Dienstag, 19. Juli 2011 16:59
>> An: general-ide
>> Betreff: Re: AW: Momentix IDE Debugger Error
>>
>> Debug and Release are in different directories on target or on host? How do you launch? Do you upload binary and all 
libraries every time?
>>
>> On 07/19/2011 10:51 AM, Andreas Beschorner wrote:
>>> Greetings Elena and Aleksandar,
>>>
>>> @Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library 
confusion. For large programs, your advice or different or unwanted behaviour is true, but the small program attached 
should really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can do.
>>>
>>> @Aleksandar: Find attached a zip-file with 5 images debugXX.png,
>>> 01) Starting the debugger and stopping at the  breakpoint where the reference is created
>>> 02 .. 04) After pressing F6 once each time
>>> 0x) Several F6 presses later
>>>
>>> I also included the disassembly which shows that basically indirect addresses seem ok....
>>>
>>> Best regards and thanks in advance for help,
>>> Andreas
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> General
>>> http://community.qnx.com/sf/go/post87431
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post87432
>>
>>
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post87435
> 
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
> 
> 
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post87437
RE: AW: AW: Momentix IDE Debugger Error  
Ahem, what do you mean by saying I do not use a proper way of debugging?? I made things as problemless as possible by 
using scripts and commands to avoid problems coming from run configurations where multiple applications access identical
 libraries which leads to conflicts, as you cannot upload libraries already in use. I use different directories for 
release and debug version avoiding library mess, and the consoles do not show any errors at all. That is basically what 
you suggested but additionally avoiding potential problems in your setup...

Hope I do not sound rude, sorry if so.

Regards,
G.

________________________________________
From: Elena Laskavaia [community-noreply@qnx.com]
Sent: Tuesday, July 19, 2011 8:08 PM
To: general-ide
Subject: Re: AW: AW: Momentix IDE Debugger Error

If you not using proper way of debugging I cannot really help you.

On 07/19/2011 01:51 PM, Andreas Beschorner wrote:
> I wrote a script using samba client copy commands which connects to the windows platform and copies all necessary 
libraries and executables, so I do not need to start any launch configuration and thus do not run into problems when 
several apps access the same libs, which often leads to "already in use" conflicts.
> And all checks are done: Nothing missing and no incorrect libraries involved.
>
> Regards,
> A.
>
> ________________________________________
> From: Elena Laskavaia [community-noreply@qnx.com]
> Sent: Tuesday, July 19, 2011 5:11 PM
> To: general-ide
> Subject: Re: AW: AW: Momentix IDE Debugger Error
>
> Try using qnx launch configurations which upload binary for you (and related library if you have custom libraries)
> Also check the console for errors especially for mismatches.
>
> On 07/19/2011 11:01 AM, Andreas Beschorner wrote:
>> Hoi,
>>
>> yes, I either upload or drag&drop them manually and execute them on the target. When testing, nothing can be too save!
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Elena Laskavaia [mailto:community-noreply@qnx.com]
>> Gesendet: Dienstag, 19. Juli 2011 16:59
>> An: general-ide
>> Betreff: Re: AW: Momentix IDE Debugger Error
>>
>> Debug and Release are in different directories on target or on host? How do you launch? Do you upload binary and all 
libraries every time?
>>
>> On 07/19/2011 10:51 AM, Andreas Beschorner wrote:
>>> Greetings Elena and Aleksandar,
>>>
>>> @Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library 
confusion. For large programs, your advice or different or unwanted behaviour is true, but the small program attached 
should really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can do.
>>>
>>> @Aleksandar: Find attached a zip-file with 5 images debugXX.png,
>>> 01) Starting the debugger and stopping at the  breakpoint where the reference is created
>>> 02 .. 04) After pressing F6 once each time
>>> 0x) Several F6 presses later
>>>
>>> I also included the disassembly which shows that basically indirect addresses seem ok....
>>>
>>> Best regards and thanks in advance for help,
>>> Andreas
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> General
>>> http://community.qnx.com/sf/go/post87431
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post87432
>>
>>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post87435
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be...
Post Deleted
Re: AW: AW: Momentix IDE Debugger Error  
If you avoiding safety guards and uploading new libraries on top of ones which are used by debugger already this may 
cause problems, 
there is a reason why IDE does not do that.

On 07/19/2011 03:00 PM, Andreas Beschorner wrote:
> Ahem, what do you mean by saying I do not use a proper way of debugging?? I made things as problemless as possible by 
using scripts and commands to avoid problems coming from run configurations where multiple applications access identical
 libraries which leads to conflicts, as you cannot upload libraries already in use. I use different directories for 
release and debug version avoiding library mess, and the consoles do not show any errors at all. That is basically what 
you suggested but additionally avoiding potential problems in your setup...
> 
> Hope I do not sound rude, sorry if so.
> 
> Regards,
> G.
> 
> ________________________________________
> From: Elena Laskavaia [community-noreply@qnx.com]
> Sent: Tuesday, July 19, 2011 8:08 PM
> To: general-ide
> Subject: Re: AW: AW: Momentix IDE Debugger Error
> 
> If you not using proper way of debugging I cannot really help you.
> 
> On 07/19/2011 01:51 PM, Andreas Beschorner wrote:
>> I wrote a script using samba client copy commands which connects to the windows platform and copies all necessary 
libraries and executables, so I do not need to start any launch configuration and thus do not run into problems when 
several apps access the same libs, which often leads to "already in use" conflicts.
>> And all checks are done: Nothing missing and no incorrect libraries involved.
>>
>> Regards,
>> A.
>>
>> ________________________________________
>> From: Elena Laskavaia [community-noreply@qnx.com]
>> Sent: Tuesday, July 19, 2011 5:11 PM
>> To: general-ide
>> Subject: Re: AW: AW: Momentix IDE Debugger Error
>>
>> Try using qnx launch configurations which upload binary for you (and related library if you have custom libraries)
>> Also check the console for errors especially for mismatches.
>>
>> On 07/19/2011 11:01 AM, Andreas Beschorner wrote:
>>> Hoi,
>>>
>>> yes, I either upload or drag&drop them manually and execute them on the target. When testing, nothing can be too save!
>>>
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Elena Laskavaia [mailto:community-noreply@qnx.com]
>>> Gesendet: Dienstag, 19. Juli 2011 16:59
>>> An: general-ide
>>> Betreff: Re: AW: Momentix IDE Debugger Error
>>>
>>> Debug and Release are in different directories on target or on host? How do you launch? Do you upload binary and all
 libraries every time?
>>>
>>> On 07/19/2011 10:51 AM, Andreas Beschorner wrote:
>>>> Greetings Elena and Aleksandar,
>>>>
>>>> @Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library 
confusion. For large programs, your advice or different or unwanted behaviour is true, but the small program attached 
should really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can do.
>>>>
>>>> @Aleksandar: Find attached a zip-file with 5 images debugXX.png,
>>>> 01) Starting the debugger and stopping at the  breakpoint where the reference is created
>>>> 02 .. 04) After pressing F6 once each time
>>>> 0x) Several F6 presses later
>>>>
>>>> I also included the disassembly which shows that basically indirect addresses seem ok....
>>>>
>>>> Best regards and thanks in advance for help,
>>>> Andreas
>>>>
>>>>
>>>>
>>>>
>>>>...
View Full Message
RE: AW: AW: Momentix IDE Debugger Error  
I think there is a misunderstanding -- I upload exactly the things created by Momentix, just not via run config but from
 the qnx console using the samba client it offers. Trust me, it avoids this problem of uploading libraries which are in 
use, as one uploads all (just once) without starting anything. That avoids conflicts!
No new on top of others, just not multiple copies of one and the same lib while programs are already running....
Trust me, ignoring nothing from the IDE here!

________________________________________
From: Elena Laskavaia [community-noreply@qnx.com]
Sent: Tuesday, July 19, 2011 9:19 PM
To: general-ide
Subject: Re: AW: AW: Momentix IDE Debugger Error

If you avoiding safety guards and uploading new libraries on top of ones which are used by debugger already this may 
cause problems,
there is a reason why IDE does not do that.

On 07/19/2011 03:00 PM, Andreas Beschorner wrote:
> Ahem, what do you mean by saying I do not use a proper way of debugging?? I made things as problemless as possible by 
using scripts and commands to avoid problems coming from run configurations where multiple applications access identical
 libraries which leads to conflicts, as you cannot upload libraries already in use. I use different directories for 
release and debug version avoiding library mess, and the consoles do not show any errors at all. That is basically what 
you suggested but additionally avoiding potential problems in your setup...
>
> Hope I do not sound rude, sorry if so.
>
> Regards,
> G.
>
> ________________________________________
> From: Elena Laskavaia [community-noreply@qnx.com]
> Sent: Tuesday, July 19, 2011 8:08 PM
> To: general-ide
> Subject: Re: AW: AW: Momentix IDE Debugger Error
>
> If you not using proper way of debugging I cannot really help you.
>
> On 07/19/2011 01:51 PM, Andreas Beschorner wrote:
>> I wrote a script using samba client copy commands which connects to the windows platform and copies all necessary 
libraries and executables, so I do not need to start any launch configuration and thus do not run into problems when 
several apps access the same libs, which often leads to "already in use" conflicts.
>> And all checks are done: Nothing missing and no incorrect libraries involved.
>>
>> Regards,
>> A.
>>
>> ________________________________________
>> From: Elena Laskavaia [community-noreply@qnx.com]
>> Sent: Tuesday, July 19, 2011 5:11 PM
>> To: general-ide
>> Subject: Re: AW: AW: Momentix IDE Debugger Error
>>
>> Try using qnx launch configurations which upload binary for you (and related library if you have custom libraries)
>> Also check the console for errors especially for mismatches.
>>
>> On 07/19/2011 11:01 AM, Andreas Beschorner wrote:
>>> Hoi,
>>>
>>> yes, I either upload or drag&drop them manually and execute them on the target. When testing, nothing can be too save!
>>>
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Elena Laskavaia [mailto:community-noreply@qnx.com]
>>> Gesendet: Dienstag, 19. Juli 2011 16:59
>>> An: general-ide
>>> Betreff: Re: AW: Momentix IDE Debugger Error
>>>
>>> Debug and Release are in different directories on target or on host? How do you launch? Do you upload binary and all
 libraries every time?
>>>
>>> On 07/19/2011 10:51 AM, Andreas Beschorner wrote:
>>>> Greetings Elena and Aleksandar,
>>>>
>>>> @Elena: Basically, Debug and Release variant are always in separate directories, so there should be no library 
confusion. For large programs, your advice or different or unwanted behaviour is true, but the small program attached 
should really make no trouble :-) Thanks for the information about the mudflap problems, I will see what I can...
View Full Message
Re: AW: AW: Momentix IDE Debugger Error  
We back to squire one - we need debug log to diagnose anything

On 07/19/2011 03:25 PM, Andreas Beschorner wrote:
> I think there is a misunderstanding -- I upload exactly the things created by Momentix, just not via run config but 
from the qnx console using the samba client it offers. Trust me, it avoids this problem of uploading libraries which are
 in use, as one uploads all (just once) without starting anything. That avoids conflicts!
> No new on top of others, just not multiple copies of one and the same lib while programs are already running....
> Trust me, ignoring nothing from the IDE here!
> 
>
RE: AW: AW: Momentix IDE Debugger Error  
The pics did not help? How can I produce a debug log via IDE? Or do I have to switch do command line debugging?
Thanks for help here, going to bed soon so I will be back tomorrow.

Thanks a lot to all helping here!
Andy
________________________________________
From: Elena Laskavaia [community-noreply@qnx.com]
Sent: Tuesday, July 19, 2011 9:32 PM
To: general-ide
Subject: Re: AW: AW: Momentix IDE Debugger Error

We back to squire one - we need debug log to diagnose anything

On 07/19/2011 03:25 PM, Andreas Beschorner wrote:
> I think there is a misunderstanding -- I upload exactly the things created by Momentix, just not via run config but 
from the qnx console using the samba client it offers. Trust me, it avoids this problem of uploading libraries which are
 in use, as one uploads all (just once) without starting anything. That avoids conflicts!
> No new on top of others, just not multiple copies of one and the same lib while programs are already running....
> Trust me, ignoring nothing from the IDE here!
>
>



_______________________________________________

General
http://community.qnx.com/sf/go/post87445


--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.

Re: AW: AW: Momentix IDE Debugger Error  
Pictures don't help they don't have debug log. You need to copy log from console when gdb "item" is selected in Debug 
view.

On 07/19/2011 04:02 PM, Andreas Beschorner wrote:
> The pics did not help? How can I produce a debug log via IDE? Or do I have to switch do command line debugging?
> Thanks for help here, going to bed soon so I will be back tomorrow.
> 
> Thanks a lot to all helping here!
> Andy
> ________________________________________
> From: Elena Laskavaia [community-noreply@qnx.com]
> Sent: Tuesday, July 19, 2011 9:32 PM
> To: general-ide
> Subject: Re: AW: AW: Momentix IDE Debugger Error
> 
> We back to squire one - we need debug log to diagnose anything
> 
> On 07/19/2011 03:25 PM, Andreas Beschorner wrote:
>> I think there is a misunderstanding -- I upload exactly the things created by Momentix, just not via run config but 
from the qnx console using the samba client it offers. Trust me, it avoids this problem of uploading libraries which are
 in use, as one uploads all (just once) without starting anything. That avoids conflicts!
>> No new on top of others, just not multiple copies of one and the same lib while programs are already running....
>> Trust me, ignoring nothing from the IDE here!
>>
>>
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post87445
> 
> 
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
> 
> 
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post87447
> 
RE: AW: AW: Momentix IDE Debugger Error  
From your question and replies so far I can see you are not using the
IDE debug launch. You can certainly use command line debugging with your
customized debug process, but if you want to use the IDE you need to
follow the below guidelines to properly setup the IDE debug launch so
IDE can connect the debug views to your program:

- Launch Configurations Reference
http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.ide.userguide
/topic/launch_Base_.html

- Debugging in the IDE
http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.ide.userguide
/topic/debug_Base_.html

HTH,
(another)Andy

-----Original Message-----
From: Andreas Beschorner [mailto:community-noreply@qnx.com] 
Sent: July-19-11 4:03 PM
To: general-ide
Subject: RE: AW: AW: Momentix IDE Debugger Error

The pics did not help? How can I produce a debug log via IDE? Or do I
have to switch do command line debugging?
Thanks for help here, going to bed soon so I will be back tomorrow.

Thanks a lot to all helping here!
Andy
AW: AW: AW: Momentix IDE Debugger Error  
Ok, same results with using just a debug configuration (btw I also debugged via config, I just do not use it to upload 
necessary libraries... This seems not to have become clear). No difference at all. So how can I get the debug log in the
 IDE? I tried to find a verbosity parameter but without success. And copying the stack does not give more information 
than the images I attached.

Thanks for help here,
Andy

-----Ursprüngliche Nachricht-----
Von: Andy Jin [mailto:community-noreply@qnx.com] 
Gesendet: Dienstag, 19. Juli 2011 22:16
An: general-ide
Betreff: RE: AW: AW: Momentix IDE Debugger Error

From your question and replies so far I can see you are not using the
IDE debug launch. You can certainly use command line debugging with your
customized debug process, but if you want to use the IDE you need to
follow the below guidelines to properly setup the IDE debug launch so
IDE can connect the debug views to your program:

- Launch Configurations Reference
http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.ide.userguide
/topic/launch_Base_.html

- Debugging in the IDE
http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.ide.userguide
/topic/debug_Base_.html

HTH,
(another)Andy

-----Original Message-----
From: Andreas Beschorner [mailto:community-noreply@qnx.com] 
Sent: July-19-11 4:03 PM
To: general-ide
Subject: RE: AW: AW: Momentix IDE Debugger Error

The pics did not help? How can I produce a debug log via IDE? Or do I
have to switch do command line debugging?
Thanks for help here, going to bed soon so I will be back tomorrow.

Thanks a lot to all helping here!
Andy




_______________________________________________

General
http://community.qnx.com/sf/go/post87450


-- 
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
Re: AW: AW: AW: Momentix IDE Debugger Error  
I already explained. Just click on gdb process in the Debug view. Open Console view and copy result to us.
To increase verbosity there is a flag in Debug tab of launch configuration.

On 07/20/2011 03:01 AM, Andreas Beschorner wrote:
> Ok, same results with using just a debug configuration (btw I also debugged via config, I just do not use it to upload
 necessary libraries... This seems not to have become clear). No difference at all. So how can I get the debug log in 
the IDE? I tried to find a verbosity parameter but without success. And copying the stack does not give more information
 than the images I attached.
> 
> Thanks for help here,
> Andy
> 
> -----Ursprüngliche Nachricht-----
> Von: Andy Jin [mailto:community-noreply@qnx.com] 
> Gesendet: Dienstag, 19. Juli 2011 22:16
> An: general-ide
> Betreff: RE: AW: AW: Momentix IDE Debugger Error
> 
> From your question and replies so far I can see you are not using the
> IDE debug launch. You can certainly use command line debugging with your
> customized debug process, but if you want to use the IDE you need to
> follow the below guidelines to properly setup the IDE debug launch so
> IDE can connect the debug views to your program:
> 
> - Launch Configurations Reference
> http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.ide.userguide
> /topic/launch_Base_.html
> 
> - Debugging in the IDE
> http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.ide.userguide
> /topic/debug_Base_.html
> 
> HTH,
> (another)Andy
> 
> -----Original Message-----
> From: Andreas Beschorner [mailto:community-noreply@qnx.com] 
> Sent: July-19-11 4:03 PM
> To: general-ide
> Subject: RE: AW: AW: Momentix IDE Debugger Error
> 
> The pics did not help? How can I produce a debug log via IDE? Or do I
> have to switch do command line debugging?
> Thanks for help here, going to bed soon so I will be back tomorrow.
> 
> Thanks a lot to all helping here!
> Andy
> 
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post87450
> 
> 
Re: AW: AW: AW: Momentix IDE Debugger Error  
Ah, yes, thanks Elena,

here we go with I hope helpfull debug output from the small app, again starting and stepping over with F6. It is quite 
long though...:

.gdbinit: No such file or directory.
206-gdb-set confirm off
206^done
(gdb) 
207-gdb-set width 0
207^done
(gdb) 
208-gdb-set height 0
208^done
(gdb) 
209-interpreter-exec console echo
209^done
(gdb) 
210-gdb-show prompt
210^done,value="(gdb) "
(gdb) 
211-target-select qnx 192.168.243.3:8000
~"MsgNak received - resending\n"
MsgNak received - resending
~"Remote target is little-endian\n"
Remote target is little-endian
211^connected
(gdb) 
212-gdb-set auto-solib-add on
212^done
(gdb) 
213-gdb-set stop-on-solib-events 0
213^done
(gdb) 
214-gdb-set stop-on-solib-events 1
214^done
(gdb) 
215 attach 5038122
&"attach 5038122\n"
attach 5038122
~"[New pid 5038122 tid 1]\n"
[New pid 5038122 tid 1]
~"0xb033f7e0 in ?? ()\n"
0xb033f7e0 in ?? ()
215^done
(gdb) 
216-environment-directory C:/coding/projects/wm201106Base/workspace/testBug C:/coding/projects/wm201106Base/workspace/
testBug/x86 C:/coding/projects/wm201106Base/workspace/testBug/x86/o C:/coding/projects/wm201106Base/workspace/testBug/
x86/o-g
216^done,source-path="C:/coding/projects/wm201106Base/workspace/testBug;C:/coding/projects/wm201106Base/workspace/
testBug/x86;C:/coding/projects/wm201106Base/workspace/testBug/x86/o;C:/coding/projects/wm201106Base/workspace/testBug/
x86/o-g;$cdir;$cwd"
(gdb) 
217 info tidinfo
&"info tidinfo\n"
~"Threads for pid 5038122 (C:\\coding\\projects\\wm201106Base\\workspace\\testBug\\x86\\o-g\\testBug_g)\nTid:\tState:\
tFlags:\n"
~"*1\t3\t0\n"
217^done
(gdb) 
218-data-list-register-names
218^done,register-names=["eax","ecx","edx","ebx","esp","ebp","esi","edi","eip","eflags","cs","ss","ds","es","fs","gs","
st0","st1","st2","st3","st4","st5","st6","st7","fctrl","fstat","ftag","fiseg","fioff","foseg","fooff","fop","xmm0","xmm1
","xmm2","xmm3","xmm4","xmm5","xmm6","xmm7","mxcsr","mm0","mm1","mm2","mm3","mm4","mm5","mm6","mm7"]
(gdb) 
219-stack-info-depth
219^done,depth="1"
(gdb) 
220-break-insert wmLoggerTest.cc:359
&"No source file named wmLoggerTest.cc.\n"
No source file named wmLoggerTest.cc.
220^error,msg="No source file named wmLoggerTest.cc."
(gdb) 
221-stack-list-frames 0 1
221^done,stack=[frame={level="0",addr="0xb033f7e0",func="??"}]
(gdb) 
222-break-insert testBug.cc:17
222^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x08048909",func="main",file="C:/coding/
projects/wm201106Base/workspace/testBug/testBug.cc",fullname="C:/coding/projects/wm201106Base/workspace/testBug/testBug.
cc",line="17",times="0"}
(gdb) 
223-break-insert testBug.cc:12
223^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="0x08048996",func="
__static_initialization_and_destruction_0",file="C:/coding/projects/wm201106Base/workspace/testBug/testBug.cc",fullname=
"C:/coding/projects/wm201106Base/workspace/testBug/testBug.cc",line="12",times="0"}
(gdb) 
224-break-insert testBug.cc:13
224^done,bkpt={number="3",type="breakpoint",disp="keep",enabled="y",addr="0x08048996",func="
__static_initialization_and_destruction_0",file="C:/coding/projects/wm201106Base/workspace/testBug/testBug.cc",fullname=
"C:/coding/projects/wm201106Base/workspace/testBug/testBug.cc",line="13",times="0"}
(gdb) 
225-break-insert -t main
225^done,bkpt={number="4",type="breakpoint",disp="del",enabled="y",addr="0x08048909",func="main",file="C:/coding/
projects/wm201106Base/workspace/testBug/testBug.cc",fullname="C:/coding/projects/wm201106Base/workspace/testBug/testBug.
cc",line="17",times="0"}
(gdb) 
226-exec-continue
226^running
(gdb) 
&"warning: Host file C:/coding/QNX650/target/qnx6/x86/lib/libc.so.3 does not match target file.\n"
warning: Host file C:/coding/QNX650/target/qnx6/x86/lib/libc.so.3 does not match target file.
~"Stopped due to shared library event\n"
Stopped due to shared library event
226*stopped,thread-id="1"
(gdb) 
227...
View Full Message
Re: AW: AW: AW: Momentix IDE Debugger Error  
On 07/20/2011 10:11 AM, Andreas Beschorner wrote:
> &"warning: Host file C:/coding/QNX650/target/qnx6/x86/lib/libc.so.3 does not match target file.\n"
> warning: Host file C:/coding/QNX650/target/qnx6/x86/lib/libc.so.3 does not match target file.

This is the most likely culprit of your troubles. You need matching 
libraries on your host and target.

How did you get mismatching libc? Is the target not running a 6.5.0? 
Have you, by any chance, applied patches on the host but not updated the 
target image?
AW: AW: AW: AW: Momentix IDE Debugger Error  
Hoi,
I remember we had this warning some time ago already. I just updated completely to 6.5.0 two weeks ago, the new target 
is definitely 6.5.0 and so is the Momentix environment (as you have already seen with the information I gave about the 
gcc version...)
I must admit I have no idea where this problems stems from. I will check the update question and be back as soon as I 
know more about this.

Thanks so far,
Andy

-----Ursprüngliche Nachricht-----
Von: Aleksandar Ristovski [mailto:community-noreply@qnx.com] 
Gesendet: Mittwoch, 20. Juli 2011 16:42
An: general-ide
Betreff: Re: AW: AW: AW: Momentix IDE Debugger Error

On 07/20/2011 10:11 AM, Andreas Beschorner wrote:
> &"warning: Host file C:/coding/QNX650/target/qnx6/x86/lib/libc.so.3 does not match target file.\n"
> warning: Host file C:/coding/QNX650/target/qnx6/x86/lib/libc.so.3 does not match target file.

This is the most likely culprit of your troubles. You need matching 
libraries on your host and target.

How did you get mismatching libc? Is the target not running a 6.5.0? 
Have you, by any chance, applied patches on the host but not updated the 
target image?



_______________________________________________

General
http://community.qnx.com/sf/go/post87469


-- 
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
Re: AW: AW: AW: AW: Momentix IDE Debugger Error  
Back again.

libc.so.3 is really different in size and date of creation -- but I honestly have no idea how this can happen, as both 
target and host were downloaded/ created just 3 or 4 weeks ago and should be the same.

The date of creation for most libs (all on the target) is June or July 2010, whereas libc.so.3 on the windows machine 
(host) is dated 2011/02/25.

Really strange. I will try using the same lib (I will give both a shot) and see what happens.

Until later and thank you very much,
Andy
Re: AW: AW: AW: AW: Momentix IDE Debugger Error  
Re.

After using identical libraries the debugger does not crash any longer. However, the path when stepping through it is 
still strange, and the static initialization results in a lot of missing information.

Here the output of a run without a static array and its initialization and one including it (the latter starting at the 
line ---p2):

Best regards,
Andy
---------------------

---p1
.gdbinit: No such file or directory.
2602-gdb-set confirm off
2602^done
(gdb) 
2603-gdb-set width 0
2603^done
(gdb) 
2604-gdb-set height 0
2604^done
(gdb) 
2605-interpreter-exec console echo
2605^done
(gdb) 
2606-gdb-show prompt
2606^done,value="(gdb) "
(gdb) 
2607-target-select qnx 192.168.243.3:8000
~"MsgNak received - resending\n"
MsgNak received - resending
~"Remote target is little-endian\n"
Remote target is little-endian
2607^connected
(gdb) 
2608-gdb-set auto-solib-add on
2608^done
(gdb) 
2609-gdb-set stop-on-solib-events 0
2609^done
(gdb) 
2610-gdb-set stop-on-solib-events 1
2610^done
(gdb) 
2611 attach 6791228
&"attach 6791228\n"
attach 6791228
~"[New pid 6791228 tid 1]\n"
[New pid 6791228 tid 1]
~"0xb033f7e0 in ?? ()\n"
0xb033f7e0 in ?? ()
2611^done
(gdb) 
2612-environment-directory C:/coding/projects/wm201106Base/workspace/testBug C:/coding/projects/wm201106Base/workspace/
testBug/x86 C:/coding/projects/wm201106Base/workspace/testBug/x86/o C:/coding/projects/wm201106Base/workspace/testBug/
x86/o-g
2612^done,source-path="C:/coding/projects/wm201106Base/workspace/testBug;C:/coding/projects/wm201106Base/workspace/
testBug/x86;C:/coding/projects/wm201106Base/workspace/testBug/x86/o;C:/coding/projects/wm201106Base/workspace/testBug/
x86/o-g;$cdir;$cwd"
(gdb) 
2613 info tidinfo
&"info tidinfo\n"
~"Threads for pid 6791228 (C:\\coding\\projects\\wm201106Base\\workspace\\testBug\\x86\\o-g\\testBug_g)\nTid:\tState:\
tFlags:\n"
~"*1\t3\t0\n"
2613^done
(gdb) 
2614-data-list-register-names
2614^done,register-names=["eax","ecx","edx","ebx","esp","ebp","esi","edi","eip","eflags","cs","ss","ds","es","fs","gs","
st0","st1","st2","st3","st4","st5","st6","st7","fctrl","fstat","ftag","fiseg","fioff","foseg","fooff","fop","xmm0","xmm1
","xmm2","xmm3","xmm4","xmm5","xmm6","xmm7","mxcsr","mm0","mm1","mm2","mm3","mm4","mm5","mm6","mm7"]
(gdb) 
2615-stack-info-depth
2615^done,depth="1"
(gdb) 
2616-break-insert wmLoggerTest.cc:359
&"No source file named wmLoggerTest.cc.\n"
No source file named wmLoggerTest.cc.
2616^error,msg="No source file named wmLoggerTest.cc."
(gdb) 
2617-stack-list-frames 0 1
2617^done,stack=[frame={level="0",addr="0xb033f7e0",func="??"}]
(gdb) 
2618-break-insert testBug.cc:22
2618^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0804897b",func="main",file="C:/coding/
projects/wm201106Base/workspace/testBug/testBug.cc",fullname="C:/coding/projects/wm201106Base/workspace/testBug/testBug.
cc",line="22",times="0"}
(gdb) 
2619-break-insert testBug.cc:17
2619^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="0x08048970",func="main",file="C:/coding/
projects/wm201106Base/workspace/testBug/testBug.cc",fullname="C:/coding/projects/wm201106Base/workspace/testBug/testBug.
cc",line="17",times="0"}
(gdb) 
2620-break-insert testBug.cc:18
2620^done,bkpt={number="3",type="breakpoint",disp="keep",enabled="y",addr="0x08048970",func="main",file="C:/coding/
projects/wm201106Base/workspace/testBug/testBug.cc",fullname="C:/coding/projects/wm201106Base/workspace/testBug/testBug.
cc",line="18",times="0"}
(gdb) 
2621-break-insert wmLoggerTest.cc:358
&"No source file named wmLoggerTest.cc.\n"
2621^error,msg="No source file named wmLoggerTest.cc."
No source file named wmLoggerTest.cc.
(gdb) 
2622-break-insert wmLogger.h:1151
&"No source file named wmLogger.h.\n"
No source file named wmLogger.h.
2622^error,msg="No source file named wmLogger.h."
(gdb) 
2623-break-insert wmLogger.h:1193
&"No source file named...
View Full Message
Re: AW: AW: AW: AW: Momentix IDE Debugger Error  
Did you compile with -g -O0
?

On 07/20/2011 11:54 AM, Andreas Beschorner wrote:
> Re.
> 
> After using identical libraries the debugger does not crash any longer. However, the path when stepping through it is 
still strange, and the static initialization results in a lot of missing information.
> 
> Here the output of a run without a static array and its initialization and one including it (the latter starting at 
the line ---p2):
> 
> Best regards,
> Andy
> ---------------------
> 
> ---p1
> .gdbinit: No such file or directory.
> 2602-gdb-set confirm off
> 2602^done
> (gdb) 
> 2603-gdb-set width 0
> 2603^done
> (gdb) 
> 2604-gdb-set height 0
> 2604^done
> (gdb) 
> 2605-interpreter-exec console echo
> 2605^done
> (gdb) 
> 2606-gdb-show prompt
> 2606^done,value="(gdb) "
> (gdb) 
> 2607-target-select qnx 192.168.243.3:8000
> ~"MsgNak received - resending\n"
> MsgNak received - resending
> ~"Remote target is little-endian\n"
> Remote target is little-endian
> 2607^connected
> (gdb) 
> 2608-gdb-set auto-solib-add on
> 2608^done
> (gdb) 
> 2609-gdb-set stop-on-solib-events 0
> 2609^done
> (gdb) 
> 2610-gdb-set stop-on-solib-events 1
> 2610^done
> (gdb) 
> 2611 attach 6791228
> &"attach 6791228\n"
> attach 6791228
> ~"[New pid 6791228 tid 1]\n"
> [New pid 6791228 tid 1]
> ~"0xb033f7e0 in ?? ()\n"
> 0xb033f7e0 in ?? ()
> 2611^done
> (gdb) 
> 2612-environment-directory C:/coding/projects/wm201106Base/workspace/testBug C:/coding/projects/wm201106Base/workspace
/testBug/x86 C:/coding/projects/wm201106Base/workspace/testBug/x86/o C:/coding/projects/wm201106Base/workspace/testBug/
x86/o-g
> 2612^done,source-path="C:/coding/projects/wm201106Base/workspace/testBug;C:/coding/projects/wm201106Base/workspace/
testBug/x86;C:/coding/projects/wm201106Base/workspace/testBug/x86/o;C:/coding/projects/wm201106Base/workspace/testBug/
x86/o-g;$cdir;$cwd"
> (gdb) 
> 2613 info tidinfo
> &"info tidinfo\n"
> ~"Threads for pid 6791228 (C:\\coding\\projects\\wm201106Base\\workspace\\testBug\\x86\\o-g\\testBug_g)\nTid:\tState
:\tFlags:\n"
> ~"*1\t3\t0\n"
> 2613^done
> (gdb) 
> 2614-data-list-register-names
> 2614^done,register-names=["eax","ecx","edx","ebx","esp","ebp","esi","edi","eip","eflags","cs","ss","ds","es","fs","gs"
,"st0","st1","st2","st3","st4","st5","st6","st7","fctrl","fstat","ftag","fiseg","fioff","foseg","fooff","fop","xmm0","
xmm1","xmm2","xmm3","xmm4","xmm5","xmm6","xmm7","mxcsr","mm0","mm1","mm2","mm3","mm4","mm5","mm6","mm7"]
> (gdb) 
> 2615-stack-info-depth
> 2615^done,depth="1"
> (gdb) 
> 2616-break-insert wmLoggerTest.cc:359
> &"No source file named wmLoggerTest.cc.\n"
> No source file named wmLoggerTest.cc.
> 2616^error,msg="No source file named wmLoggerTest.cc."
> (gdb) 
> 2617-stack-list-frames 0 1
> 2617^done,stack=[frame={level="0",addr="0xb033f7e0",func="??"}]
> (gdb) 
> 2618-break-insert testBug.cc:22
> 2618^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0804897b",func="main",file="C:/coding/
projects/wm201106Base/workspace/testBug/testBug.cc",fullname="C:/coding/projects/wm201106Base/workspace/testBug/testBug.
cc",line="22",times="0"}
> (gdb) 
> 2619-break-insert testBug.cc:17
> 2619^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="0x08048970",func="main",file="C:/coding/
projects/wm201106Base/workspace/testBug/testBug.cc",fullname="C:/coding/projects/wm201106Base/workspace/testBug/testBug.
cc",line="17",times="0"}
> (gdb) 
> 2620-break-insert testBug.cc:18
>...
View Full Message
AW: AW: AW: AW: AW: Momentix IDE Debugger Error  
Greetings,

Yes, I have no optimization and tried different levels of debug information. Same results.

-----Ursprüngliche Nachricht-----
Von: Elena Laskavaia [mailto:community-noreply@qnx.com] 
Gesendet: Mittwoch, 20. Juli 2011 18:07
An: general-ide
Betreff: Re: AW: AW: AW: AW: Momentix IDE Debugger Error

Did you compile with -g -O0
?

On 07/20/2011 11:54 AM, Andreas Beschorner wrote:
> Re.
> 
> After using identical libraries the debugger does not crash any longer. However, the path when stepping through it is 
still strange, and the static initialization results in a lot of missing information.
> 
> Here the output of a run without a static array and its initialization and one including it (the latter starting at 
the line ---p2):
> 
> Best regards,
> Andy
> ---------------------
> 
> ---p1
> .gdbinit: No such file or directory.
> 2602-gdb-set confirm off
> 2602^done
> (gdb) 
> 2603-gdb-set width 0
> 2603^done
> (gdb) 
> 2604-gdb-set height 0
> 2604^done
> (gdb) 
> 2605-interpreter-exec console echo
> 2605^done
> (gdb) 
> 2606-gdb-show prompt
> 2606^done,value="(gdb) "
> (gdb) 
> 2607-target-select qnx 192.168.243.3:8000
> ~"MsgNak received - resending\n"
> MsgNak received - resending
> ~"Remote target is little-endian\n"
> Remote target is little-endian
> 2607^connected
> (gdb) 
> 2608-gdb-set auto-solib-add on
> 2608^done
> (gdb) 
> 2609-gdb-set stop-on-solib-events 0
> 2609^done
> (gdb) 
> 2610-gdb-set stop-on-solib-events 1
> 2610^done
> (gdb) 
> 2611 attach 6791228
> &"attach 6791228\n"
> attach 6791228
> ~"[New pid 6791228 tid 1]\n"
> [New pid 6791228 tid 1]
> ~"0xb033f7e0 in ?? ()\n"
> 0xb033f7e0 in ?? ()
> 2611^done
> (gdb) 
> 2612-environment-directory C:/coding/projects/wm201106Base/workspace/testBug C:/coding/projects/wm201106Base/workspace
/testBug/x86 C:/coding/projects/wm201106Base/workspace/testBug/x86/o C:/coding/projects/wm201106Base/workspace/testBug/
x86/o-g
> 2612^done,source-path="C:/coding/projects/wm201106Base/workspace/testBug;C:/coding/projects/wm201106Base/workspace/
testBug/x86;C:/coding/projects/wm201106Base/workspace/testBug/x86/o;C:/coding/projects/wm201106Base/workspace/testBug/
x86/o-g;$cdir;$cwd"
> (gdb) 
> 2613 info tidinfo
> &"info tidinfo\n"
> ~"Threads for pid 6791228 (C:\\coding\\projects\\wm201106Base\\workspace\\testBug\\x86\\o-g\\testBug_g)\nTid:\tState
:\tFlags:\n"
> ~"*1\t3\t0\n"
> 2613^done
> (gdb) 
> 2614-data-list-register-names
> 2614^done,register-names=["eax","ecx","edx","ebx","esp","ebp","esi","edi","eip","eflags","cs","ss","ds","es","fs","gs"
,"st0","st1","st2","st3","st4","st5","st6","st7","fctrl","fstat","ftag","fiseg","fioff","foseg","fooff","fop","xmm0","
xmm1","xmm2","xmm3","xmm4","xmm5","xmm6","xmm7","mxcsr","mm0","mm1","mm2","mm3","mm4","mm5","mm6","mm7"]
> (gdb) 
> 2615-stack-info-depth
> 2615^done,depth="1"
> (gdb) 
> 2616-break-insert wmLoggerTest.cc:359
> &"No source file named wmLoggerTest.cc.\n"
> No source file named wmLoggerTest.cc.
> 2616^error,msg="No source file named wmLoggerTest.cc."
> (gdb) 
> 2617-stack-list-frames 0 1
> 2617^done,stack=[frame={level="0",addr="0xb033f7e0",func="??"}]
> (gdb) 
> 2618-break-insert testBug.cc:22
> 2618^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0804897b",func="main",file="C:/coding/
projects/wm201106Base/workspace/testBug/testBug.cc",fullname="C:/coding/projects/wm201106Base/workspace/testBug/testBug.
cc",line="22",times="0"}
> (gdb) 
> 2619-break-insert testBug.cc:17
>...
View Full Message
Re: AW: AW: AW: AW: AW: Momentix IDE Debugger Error  
On 07/21/2011 03:13 AM, Andreas Beschorner wrote:
> However, the path when stepping through it is still strange, and the
> static initialization results in a lot of missing information

Could you describe what is strange and what information is missing?
AW: AW: AW: AW: AW: AW: Momentix IDE Debugger Error  
Sure thing:
Strange is that after initialization the debugging cursor firs jumps to the end of the main function. After this, the 
diverse missing code lines appear when continuing the stepping over or stepping in Debug (which does NOT happen when not
 initializing a static pointer with new). In the debug output this is under ---p2 and looks like

> 2739-stack-list-frames 0 2
> 2739^done,stack=[frame={level="0",addr="0x08048b12",func="__do_global_ctors_aux"},frame={level="1",addr="0x08048672",
func="_init"}]
> (gdb) 
> 2740-data-list-changed-registers
> 2740^done,changed-registers=["4","5","8","16","17","18","19","20","21","22","23","32","33","34","35","36","37","38","
39"]
> (gdb) 
> 2741 info sharedlibrary
> &"info sharedlibrary\n"
> ~"From        To          Syms Read   Shared Object Library\n"
> ~"0xb8200000  0xb82f2bb4  Yes         C:/coding/QNX650/target/qnx6/x86/lib/libstdc++.so.6\n"
> ~"0xb82f3000  0xb83251e0  Yes         C:/coding/QNX650/target/qnx6/x86/lib/libm.so.2\n"
> ~"0xb0300000  0xb037e66c  Yes         C:/coding/QNX650/target/qnx6/x86/lib/libc.so.3\n"
> 2741^done
> (gdb) 
> 2742-data-disassemble -s 0x8048b12 -e 0x8048b76 -- 0
> 2742^done,asm_insns=[{address="0x08048b12",func-name="__do_global_ctors_aux",offset="50",inst="sub    $0x4,%esi"},{
address="0x08048b15",func-name="__do_global_ctors_aux",offset="53",inst="mov    (%esi),%eax"},{address="0x08048b17",func

-name="__do_global_ctors_aux",offset="55",inst="cmp    $0xffffffff,%eax"},{address="0x08048b1a",func-name="
__do_global_ctors_aux",offset="58",inst="jne    0x8048b10 <__do_global_ctors_aux+48>"},{address="0x08048b1c",func-name="

__do_global_ctors_aux",offset="60",inst="pop    %ebx"},{address="0x08048b1d",func-name="__do_global_ctors_aux",offset="
61",inst="pop    %esi"},{address="0x08048b1e",func-name="__do_global_ctors_aux",offset="62",inst="pop    %ebp"},{address

="0x08048b1f",func-name="__do_global_ctors_aux",offset="63",inst="ret    "},{address="0x08048b20",func-name="_fini",
offset="0",inst="call   0x8048860 <__do_global_dtors_aux>"},{address="0x08048b25",func-name="_fini",offset="5",inst="ret

    $0x0"},{address="0x08048b28",func-name="_fini",
of
>  fset="8",inst="push   %edi"},{address="0x08048b29",func-name="_fini",offset="9",inst="gs"},{address="0x08048b2a",func

-name="_fini",offset="10",inst="insb   (%dx),%es:(%edi)"},{address="0x08048b2b",func-name="_fini",offset="11",inst="arpl

   %bp,0x6d(%edi)"},{address="0x08048b2e",func-name="_fini",offset="14",inst="and    %dh,%gs:0x20(%edi,%ebp,2)"},{
address="0x08048b33",func-name="_fini",offset="19",inst="je     0x8048b9d <__EH_FRAME_BEGIN__+77>"},{address="0x08048b35

",func-name="_fini",offset="21",inst="and    %dl,%gs:0x4e(%ecx)"},{address="0x08048b39",func-name="_fini",offset="25",
inst="pop    %eax"},{address="0x08048b3a",func-name="_fini",offset="26",inst="and    %cl,0x6f(%ebp)"},{address="
0x08048b3d",func-name="_fini",offset="29",inst="insl   (%dx),%es:(%edi)"},{address="0x08048b3e",func-name="_fini",offset

="30",inst="outsb  %gs:(%esi),(%dx)"},{address="0x08048b40",func-name="_fini",offset="32",inst="je     0x8048bab <
__EH_FRAME_BEGIN__+91>"},{address="0x08048b42",func-
na
>  me="_fini",offset="34",inst="arpl   %si,0x20(%ebx)"},{address="0x08048b45",func-name="_fini",offset="37",inst="dec   

 %ecx"},{address="0x08048b46",func-name="_fini",offset="38",inst="inc    %esp"},{address="0x08048b47",func-name="_fini",

offset="39",inst="inc    %ebp"},{address="0x08048b48",func-name="_fini",offset="40",inst="add    %al,0x79(%ebx)"},{
address="0x08048b4b",func-name="_fini",offset="43",inst="popa   "},{address="0x08048b4c",func-name="_fini",offset="44",
inst="add    %al,(%eax)"},{address="0x08048b4e",inst="add    %al,(%eax)"},{address="0x08048b50",func-name="
__EH_FRAME_BEGIN__",offset="0",inst="sbb   ...
View Full Message
Re: AW: AW: AW: AW: AW: AW: Momentix IDE Debugger Error  
Ok. What you are seeing is not pretty but is expected. The code you are 
stepping through is a mixture of code in your executable (with debug 
line information) and code in libc (without). Jump to "the end of main" 
is an indication of debugger finding no debug line information to 
associate with the current instruction pointer.





On 07/21/2011 10:33 AM, Andreas Beschorner wrote:
> Sure thing:
> Strange is that after initialization the debugging cursor firs jumps to the end of the main function. After this, the 
diverse missing code lines appear when continuing the stepping over or stepping in Debug (which does NOT happen when not
 initializing a static pointer with new). In the debug output this is under ---p2 and looks like
>
>> 2739-stack-list-frames 0 2
>> 2739^done,stack=[frame={level="0",addr="0x08048b12",func="__do_global_ctors_aux"},frame={level="1",addr="0x08048672",

> func="_init"}]
>> (gdb)
>> 2740-data-list-changed-registers
>> 2740^done,changed-registers=["4","5","8","16","17","18","19","20","21","22","23","32","33","34","35","36","37","38","

> 39"]
>> (gdb)
>> 2741 info sharedlibrary
>> &"info sharedlibrary\n"
>> ~"From        To          Syms Read   Shared Object Library\n"
>> ~"0xb8200000  0xb82f2bb4  Yes         C:/coding/QNX650/target/qnx6/x86/lib/libstdc++.so.6\n"
>> ~"0xb82f3000  0xb83251e0  Yes         C:/coding/QNX650/target/qnx6/x86/lib/libm.so.2\n"
>> ~"0xb0300000  0xb037e66c  Yes         C:/coding/QNX650/target/qnx6/x86/lib/libc.so.3\n"
>> 2741^done
>> (gdb)
>> 2742-data-disassemble -s 0x8048b12 -e 0x8048b76 -- 0
>> 2742^done,asm_insns=[{address="0x08048b12",func-name="__do_global_ctors_aux",offset="50",inst="sub    $0x4,%esi"},{
> address="0x08048b15",func-name="__do_global_ctors_aux",offset="53",inst="mov    (%esi),%eax"},{address="0x08048b17",
func
> -name="__do_global_ctors_aux",offset="55",inst="cmp    $0xffffffff,%eax"},{address="0x08048b1a",func-name="
> __do_global_ctors_aux",offset="58",inst="jne    0x8048b10<__do_global_ctors_aux+48>"},{address="0x08048b1c",func-name=
"
> __do_global_ctors_aux",offset="60",inst="pop    %ebx"},{address="0x08048b1d",func-name="__do_global_ctors_aux",offset=
"
> 61",inst="pop    %esi"},{address="0x08048b1e",func-name="__do_global_ctors_aux",offset="62",inst="pop    %ebp"},
{address
> ="0x08048b1f",func-name="__do_global_ctors_aux",offset="63",inst="ret    "},{address="0x08048b20",func-name="_fini",
> offset="0",inst="call   0x8048860<__do_global_dtors_aux>"},{address="0x08048b25",func-name="_fini",offset="5",inst="
ret
>      $0x0"},{address="0x08048b28",func-name="_fini",
> of
>>   fset="8",inst="push   %edi"},{address="0x08048b29",func-name="_fini",offset="9",inst="gs"},{address="0x08048b2a",
func
> -name="_fini",offset="10",inst="insb   (%dx),%es:(%edi)"},{address="0x08048b2b",func-name="_fini",offset="11",inst="
arpl
>     %bp,0x6d(%edi)"},{address="0x08048b2e",func-name="_fini",offset="14",inst="and    %dh,%gs:0x20(%edi,%ebp,2)"},{
> address="0x08048b33",func-name="_fini",offset="19",inst="je     0x8048b9d<__EH_FRAME_BEGIN__+77>"},{address="
0x08048b35
> ",func-name="_fini",offset="21",inst="and    %dl,%gs:0x4e(%ecx)"},{address="0x08048b39",func-name="_fini",offset="25",

> inst="pop    %eax"},{address="0x08048b3a",func-name="_fini",offset="26",inst="and    %cl,0x6f(%ebp)"},{address="
> 0x08048b3d",func-name="_fini",offset="29",inst="insl   (%dx),%es:(%edi)"},{address="0x08048b3e",func-name="_fini",
offset
> ="30",inst="outsb  %gs:(%esi),(%dx)"},{address="0x08048b40",func-name="_fini",offset="32",inst="je     0x8048bab<
> __EH_FRAME_BEGIN__+91>"},{address="0x08048b42",func-
> na
>>   me="_fini",offset="34",inst="arpl   %si,0x20(%ebx)"},{address="0x08048b45",func-name="_fini",offset="37",inst="dec
>  ...
View Full Message
AW: AW: AW: AW: AW: AW: AW: Momentix IDE Debugger Error  
Hoi,

thanks, I guessed so, as the static object is created in the main context, which will make the IP go mad when debugging.


Thanks for all your help -- I think we can close this case now!

Greets,
Andy

-----Ursprüngliche Nachricht-----
Von: Aleksandar Ristovski [mailto:community-noreply@qnx.com] 
Gesendet: Donnerstag, 21. Juli 2011 16:42
An: general-ide
Betreff: Re: AW: AW: AW: AW: AW: AW: Momentix IDE Debugger Error

Ok. What you are seeing is not pretty but is expected. The code you are 
stepping through is a mixture of code in your executable (with debug 
line information) and code in libc (without). Jump to "the end of main" 
is an indication of debugger finding no debug line information to 
associate with the current instruction pointer.





On 07/21/2011 10:33 AM, Andreas Beschorner wrote:
> Sure thing:
> Strange is that after initialization the debugging cursor firs jumps to the end of the main function. After this, the 
diverse missing code lines appear when continuing the stepping over or stepping in Debug (which does NOT happen when not
 initializing a static pointer with new). In the debug output this is under ---p2 and looks like
>
>> 2739-stack-list-frames 0 2
>> 2739^done,stack=[frame={level="0",addr="0x08048b12",func="__do_global_ctors_aux"},frame={level="1",addr="0x08048672",

> func="_init"}]
>> (gdb)
>> 2740-data-list-changed-registers
>> 2740^done,changed-registers=["4","5","8","16","17","18","19","20","21","22","23","32","33","34","35","36","37","38","

> 39"]
>> (gdb)
>> 2741 info sharedlibrary
>> &"info sharedlibrary\n"
>> ~"From        To          Syms Read   Shared Object Library\n"
>> ~"0xb8200000  0xb82f2bb4  Yes         C:/coding/QNX650/target/qnx6/x86/lib/libstdc++.so.6\n"
>> ~"0xb82f3000  0xb83251e0  Yes         C:/coding/QNX650/target/qnx6/x86/lib/libm.so.2\n"
>> ~"0xb0300000  0xb037e66c  Yes         C:/coding/QNX650/target/qnx6/x86/lib/libc.so.3\n"
>> 2741^done
>> (gdb)
>> 2742-data-disassemble -s 0x8048b12 -e 0x8048b76 -- 0
>> 2742^done,asm_insns=[{address="0x08048b12",func-name="__do_global_ctors_aux",offset="50",inst="sub    $0x4,%esi"},{
> address="0x08048b15",func-name="__do_global_ctors_aux",offset="53",inst="mov    (%esi),%eax"},{address="0x08048b17",
func
> -name="__do_global_ctors_aux",offset="55",inst="cmp    $0xffffffff,%eax"},{address="0x08048b1a",func-name="
> __do_global_ctors_aux",offset="58",inst="jne    0x8048b10<__do_global_ctors_aux+48>"},{address="0x08048b1c",func-name=
"
> __do_global_ctors_aux",offset="60",inst="pop    %ebx"},{address="0x08048b1d",func-name="__do_global_ctors_aux",offset=
"
> 61",inst="pop    %esi"},{address="0x08048b1e",func-name="__do_global_ctors_aux",offset="62",inst="pop    %ebp"},
{address
> ="0x08048b1f",func-name="__do_global_ctors_aux",offset="63",inst="ret    "},{address="0x08048b20",func-name="_fini",
> offset="0",inst="call   0x8048860<__do_global_dtors_aux>"},{address="0x08048b25",func-name="_fini",offset="5",inst="
ret
>      $0x0"},{address="0x08048b28",func-name="_fini",
> of
>>   fset="8",inst="push   %edi"},{address="0x08048b29",func-name="_fini",offset="9",inst="gs"},{address="0x08048b2a",
func
> -name="_fini",offset="10",inst="insb   (%dx),%es:(%edi)"},{address="0x08048b2b",func-name="_fini",offset="11",inst="
arpl
>     %bp,0x6d(%edi)"},{address="0x08048b2e",func-name="_fini",offset="14",inst="and    %dh,%gs:0x20(%edi,%ebp,2)"},{
> address="0x08048b33",func-name="_fini",offset="19",inst="je     0x8048b9d<__EH_FRAME_BEGIN__+77>"},{address="
0x08048b35
> ",func-name="_fini",offset="21",inst="and    %dl,%gs:0x4e(%ecx)"},{address="0x08048b39",func-name="_fini",offset="25",

> inst="pop    %eax"},{address="0x08048b3a",func-name="_fini",offset="26",inst="and    %cl,0x6f(%ebp)"},{address="
>...
View Full Message