0 [main] ssh 1927 D:\Program Files\Git\usr\bin\ssh.exe: *** fatal error -
console device allocation failure - too many consoles in use, max consoles is 32
enter image description here
Related
I tried to debug my code with eclipse with the j-link debugger and gdb sserver and client.
I tried different settings but couldn't solve the error.
Eclipse error:
Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:2331
Error message from debugger back end:
Truncated register 16 in remote 'g' packet
Connecting to J-Link...
J-Link is connected.
Firmware: J-Link LITE-Cortex-M-5V compiled Mar 3 2016 12:49:54
GDB Server output:
Hardware: V8.00
S/N: 638100545
Feature(s): GDB
Checking target voltage...
Target voltage: 5.03 V
Listening on TCP/IP port 2331
Connecting to target...Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
GDB closed TCP/IP connection
Any hint what could solve my problem?
I'm working on establishing a debug connection to a Renesas RZ/G2L MPU.
My OpenOCD connection appears to launch fine (and i can connect to it with gdb from the shell afterwards with (gdb) target remote localhost:3333 fine):
Open On-Chip Debugger 0.12.0-rc2+dev-00989-g9501b263e-dirty (2022-12-12-17:03)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
G2L
G2L - 0 CA57(s), 2 CA55(s), 0 CA53(s), 0 CR7(s), 1 CM33(s)
Boot Core - CA55
r9a07g044l.cpu
SMP targets: r9a07g044l.a55.0 r9a07g044l.a55.1
init_reset
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : J-Link V11 compiled Dec 5 2022 13:50:41
Info : Hardware version: 11.00
Info : VTarget = 1.812 V
Info : clock speed 4000 kHz
Info : JTAG tap: r9a07g044l.cpu tap/device found: 0x6ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x6)
Info : r9a07g044l.a55.0: hardware has 6 breakpoints, 4 watchpoints
Info : starting gdb server for r9a07g044l.a55.0 on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for r9a07g044l.m33 on 3334
Info : Listening on port 3334 for gdb connections
Info : gdb port disabled
I'm trying to hook it up with eclipse to debug Flash Writer which should allow me to bring up the system. I createda debug configuration, set the init commands under start up (per instructions from Renesas) and set the launch target to localhost:3333. Upon launch of a debug session from Eclipse however, I get the following error:
Error in final launch sequence:
Failed to execute MI command:
source /home/mistywest/git/rzg2_flash_writer/gdb_smarc_g2l_flash_writer
Error message from debugger back end:
/home/mistywest/git/rzg2_flash_writer/gdb_smarc_g2l_flash_writer:12: Error in sourced command file:
Protocol error with Rcmd
Failed to execute MI command:
source /home/mistywest/git/rzg2_flash_writer/gdb_smarc_g2l_flash_writer
Error message from debugger back end:
/home/mistywest/git/rzg2_flash_writer/gdb_smarc_g2l_flash_writer:12: Error in sourced command file:
Protocol error with Rcmd
Failed to execute MI command:
source /home/mistywest/git/rzg2_flash_writer/gdb_smarc_g2l_flash_writer
Error message from debugger back end:
/home/mistywest/git/rzg2_flash_writer/gdb_smarc_g2l_flash_writer:12: Error in sourced command file:
Protocol error with Rcmd
/home/mistywest/git/rzg2_flash_writer/gdb_smarc_g2l_flash_writer:12: Error in sourced command file:\nProtocol error with Rcmd
and on the OpenOCD console:
Info : accepting 'gdb' connection on tcp/3333
Info : r9a07g044l.a55.0 cluster 0 core 0 multi core
r9a07g044l.a55.0 halted in AArch64 state due to debug-request, current mode: EL3H
cpsr: 0x400003cd pc: 0x3a94
MMU: disabled, D-Cache: disabled, I-Cache: enabled
Info : New GDB Connection: 1, Target r9a07g044l.a55.0, state: halted
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: r9a07g044l.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (0) in DAP response
Info : Deferring arp_examine of r9a07g044l.a55.1
Info : Use arp_examine command to examine it manually!
Info : Deferring arp_examine of r9a07g044l.m33
Info : Use arp_examine command to examine it manually!
Error: Invalid ACK (0) in DAP response
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: JTAG-DP STICKY ERROR
Error: Could not initialize the APB-AP
Info : dropped 'gdb' connection
Oh I'm running this from a Fedora 36 host - if it matters
I have installed Git 1.9.5 in my Windows 7 (32 bit) machine and it installed properly. I was able to clone and checkout working copy from the remote server without any trouble.
However whenever I open Git Bash it shows this error in the command prompt:
C:\Program Files\Git\bin\sh.exe: *** 1. unable to allocate heap
0x10060000, heap
_chunk_size 268435456, pid 8260, Win32 error 0
0 [main] sh.exe" 9072 sync_with_child: child 8260(0x1A4) died before
ini alization with status code 0x1 1547 [main] sh.exe" 9072
sync_with_child: *** child state waiting for longjump
sh.exe": fork: Resource temporarily unavailable
I get same error whenever I am trying to execute git pull command.
I tried to rebase the msys-1.0.dll file following this link but didn't help. Would be great if someone can help me sort it out.
Thanks in advance.
I'm having difficulties with msysgit in a windowXP 32 bit environment I would really appreciate some help with. In actual fact, I'm using SmartGit and love the program. However it fails to run both Save Stash and Clean Up. As I thought the problem was with SmartGit, I approached the developers for help. However, it turns out the problem with with msysgit.
The SmartGit I have uses msysgit 1.8.1.2 -preview20130201.
I have also installed Git-1.8.3-preview20130601 in a separate directory.
No matter which of the two versions SmartGit uses, the problems persists.
The message given by SmartGit upon trying to save a stash is:
0 [main] us 0 open_stackdumpfile: Dumping stack trace to us.stackdump
0 [main] sh.exe" 8776 sync_with_child: child 936(0x18C) died before initia
lization with status code 0xC0000005
85 [main] sh.exe" 8776 sync_with_child: *** child state waiting for longjmp
C:\Program Files\SmartGitHg 4.5\git/libexec/git-core\git-stash: fork: Resource t
emporarily unavailable
Clean Up generates the following message:
Clean Up: failed to run repack
0 [main] us 0 open_stackdumpfile: Dumping stack trace to us.stackdump
0 [main] sh.exe" 7236 sync_with_child: child 1236(0x988) died before
initialization with status code 0xC0000005
4811 [main] sh.exe" 7236 sync_with_child: *** child state waiting for longjmp
If I use the Git Gui directly (instead of SmartGit),to do the compression on the same repository, I get:
0 [main] sh.exe" 384 sync_with_child: child 7628(0x9A0) died before
initialization with status code 0xC0000005
1086 [main] sh.exe" 384 sync_with_child: *** child state waiting for longjmp
/usr/libexec/git-core/git-sh-setup: fork: Resource temporarily unavailable
If I try virtually anything with the Git Bash console, for example ls
sh.exe"-3.1$ ls
0 [main] us 0 open_stackdumpfile: Dumping stack trace to us.stackdump
68591127 [main] sh.exe" 712 sync_with_child: child 4772(0x1B4) died before initi
alization with status code 0xC0000005
68591227 [main] sh.exe" 712 sync_with_child: *** child state waiting for longjmp
sh.exe": fork: Resource temporarily unavailable
sh.exe"-3.1$
However, if I use Cygwin (git gc) on the repository, everything works fine.
I have done a web search and have found that other users have had similar error messages. The closest I found was:
Git sh.exe process forking issue on windows XP, slow?
But I don't believe that I have the same issue.
Any suggestions on what I could try would be greatly appreciated.
Thanks
Ivo
I have two computers running XP. One of them runs Git-1.8.3-preview20130601 without problems, the other doesn't. On the one that doesn't I started the machine in diagnostic startup -virtually no services running and I still have the same problem. I suppose it could be something to do with the registry?
While I running Jave ME project via Eclipse and Jave_ME_SDK_3 on Mac OS, it prompt an error on the console.I am getting Following Error
Failed to connect to device 1!
Reason:
Emulator 1 terminated while waiting for it to register