Deferent message happen on gdb:


We already replaced ntox86-gdb from regularly one to update5(rev 398)

Then happen the following message as ‘internal-error: virtual memory exhausted: can't allocate 36080 bytes’

Please let me know regarding this massage.

 
----------------------------------------
# gdb pacrun

GNU gdb 6.8 qnx-nto update 5 (rev. 398)

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 "i386-pc-nto-qnx6.3.0"...

(gdb) run

Starting program: /root/pac/Unit/Release/bin/pacrun

[New pid 1450025 tid 1]

../../gdb/utils.c:904: internal-error: virtual memory exhausted: can't allocate 36080 bytes.

A problem internal to GDB has been detected,

further debugging may prove unreliable.

Quit this debugging session? (y or n) n

 

../../gdb/utils.c:904: internal-error: virtual memory exhausted: can't allocate 36080 bytes.

A problem internal to GDB has been detected,

further debugging may prove unreliable.

Create a core file of GDB? (y or n) y

 

Program received signal 0, Signal 0.

0xb0319254 in __i686.get_pc_thunk.cx () from /usr/qnx641/target/qnx6/x86/lib/libc.so.3

(gdb) continue

Continuing.

 

Program received signal 0, Signal 0.

0xb0319254 in __i686.get_pc_thunk.cx () from /usr/qnx641/target/qnx6/x86/lib/libc.so.3

(gdb)