foundry27 : Post

Forum Topic - "Spawn error" when using pdebug upon serial to debug programs: (24 Items)

View: as

Weiming Chen

05/26/2008 10:47 PM

post8447

"Spawn error" when using pdebug upon serial to debug programs

I am trying to connect my IDE 6.3.2 under windows to my target board through pdebug upon serial port. Steps below:
1) First try a target of desktop PC with Nutrino installed. It's successful.
2) Second, build an OS image on the desktop PC using the attached build file, then write the image file to floppy disk.
Commands follow:
mkifs -v debug.build debug.ifs
dinit -f debug.ifs /dev/fd0
3) Reboot the desktop through the floppy disk, it boots up successfully without error.
4) Try to connect to the desktop target again, the error messages are:

MsgNak received - resending
MsgNak received - resending
MsgNak received - resending
Remote exhausted 3 retries.
MsgNak received - resending
MsgNak received - resending
MsgNak received - resending
Remote exhausted 3 retries.
MsgNak received - resending
MsgNak received - resending
MsgNak received - resending
Remote exhausted 3 retries.
mi_cmd_stack_list_frames: No stack.
info tidlist
Undefined info command: "tidlist". Try "help info".
set remotebaud 57600
upload C:/QNX632/prac-workspace/Hello/x86/o-g/Hello_gxx11520.tmp /tmp/Hello_g
set qnxremotecwd /tmp
Warning: /cygdrive/c/QNX632/prac-workspace/Hello/C: No such file or directory.
Warning: /QNX632/prac-workspace/Hello/.settings: No such file or directory.
Warning: /cygdrive/c/QNX632/prac-workspace/Hello/C: No such file or directory.
Warning: /QNX632/prac-workspace/Hello/x86: No such file or directory.
Warning: /cygdrive/c/QNX632/prac-workspace/Hello/C: No such file or directory.
Warning: /QNX632/prac-workspace/Hello/x86/o-g: No such file or directory.
MsgNak received - resending
MsgNak received - resending
MsgNak received - resending
Remote exhausted 3 retries.
MsgNak received - resending
MsgNak received - resending
MsgNak received - resending
Remote exhausted 3 retries.
Remote (spawn error): Exec format error.

5) I cheked the directory "\tmp" on the target, there is only an empty file (size 0) "Hello_g".
6) Anything missing when building the OS image?

Thanks
Weiming

Attachment:

debug.build 854 bytes

Elena Laskavaia

Re: "Spawn error" when using pdebug upon serial to debug programs

Elena Laskavaia

05/27/2008 9:17 AM

post8457

Re: "Spawn error" when using pdebug upon serial to debug programs

Is pdebug in /usr/bin/pdebug on the target?
In step 4 "Try to connect to the desktop" - how you are trying to 
connect? Do you use launch configuration?

Weiming Chen wrote:
> I am trying to connect my IDE 6.3.2 under windows to my target board
through pdebug upon serial port. Steps below:
> 1) First try a target of desktop PC with Nutrino installed. It's
successful.
> 2) Second, build an OS image on the desktop PC using the attached build
file, then write the image file to floppy disk. Commands follow:
>      mkifs -v debug.build debug.ifs
>      dinit -f debug.ifs /dev/fd0
> 3) Reboot the desktop through the floppy disk, it boots up successfully
without error.
> 4) Try to connect to the desktop target again, the error messages are:
>
> MsgNak received - resending
> MsgNak received - resending
> MsgNak received - resending
> Remote exhausted 3 retries.
> MsgNak received - resending
> MsgNak received - resending
> MsgNak received - resending
> Remote exhausted 3 retries.
> MsgNak received - resending
> MsgNak received - resending
> MsgNak received - resending
> Remote exhausted 3 retries.
> mi_cmd_stack_list_frames: No stack.
> info tidlist
> Undefined info command: "tidlist".  Try "help info".
> set remotebaud 57600
> upload C:/QNX632/prac-workspace/Hello/x86/o-g/Hello_gxx11520.tmp
/tmp/Hello_g
> set qnxremotecwd /tmp
> Warning: /cygdrive/c/QNX632/prac-workspace/Hello/C: No such file or
directory.
> Warning: /QNX632/prac-workspace/Hello/.settings: No such file or
directory.
> Warning: /cygdrive/c/QNX632/prac-workspace/Hello/C: No such file or
directory.
> Warning: /QNX632/prac-workspace/Hello/x86: No such file or directory.
> Warning: /cygdrive/c/QNX632/prac-workspace/Hello/C: No such file or
directory.
> Warning: /QNX632/prac-workspace/Hello/x86/o-g: No such file or directory.
> MsgNak received - resending
> MsgNak received - resending
> MsgNak received - resending
> Remote exhausted 3 retries.
> MsgNak received - resending
> MsgNak received - resending
> MsgNak received - resending
> Remote exhausted 3 retries.
> Remote (spawn error): Exec format error.
>
> 5) I cheked the directory "\tmp" on the target, there is only an empty
file (size 0) "Hello_g".
> 6) Anything missing when building the OS image?
>
> Thanks
> Weiming
>
>
>     
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post8447
>

Hans-Peter Reichert

05/27/2008 10:49 AM

post8467

AW: "Spawn error" when using pdebug upon serial to debug programs

sorry I didn't mention that I do not use the IDE to launch the binary.
I do that directly on the target, having the env set.
 

>-----Ursprüngliche Nachricht-----
>Von: Laskavaia, Elena 
>Gesendet: Dienstag, 27. Mai 2008 15:18
>An: general-ide
>Betreff: Re: "Spawn error" when using pdebug upon serial to 
>debug programs
>
>Is pdebug in /usr/bin/pdebug on the target?
>In step 4 "Try to connect to the desktop" - how you are trying 
>to connect? Do you use launch configuration?
>
>Weiming Chen wrote:
>> I am trying to connect my IDE 6.3.2 under windows to my target board
>through pdebug upon serial port. Steps below:
>> 1) First try a target of desktop PC with Nutrino installed. It's
>successful.
>> 2) Second, build an OS image on the desktop PC using the attached 
>> build
>file, then write the image file to floppy disk. Commands follow:
>>      mkifs -v debug.build debug.ifs
>>      dinit -f debug.ifs /dev/fd0
>> 3) Reboot the desktop through the floppy disk, it boots up 
>> successfully
>without error.
>> 4) Try to connect to the desktop target again, the error 
>messages are:
>>
>> MsgNak received - resending
>> MsgNak received - resending
>> MsgNak received - resending
>> Remote exhausted 3 retries.
>> MsgNak received - resending
>> MsgNak received - resending
>> MsgNak received - resending
>> Remote exhausted 3 retries.
>> MsgNak received - resending
>> MsgNak received - resending
>> MsgNak received - resending
>> Remote exhausted 3 retries.
>> mi_cmd_stack_list_frames: No stack.
>> info tidlist
>> Undefined info command: "tidlist".  Try "help info".
>> set remotebaud 57600
>> upload C:/QNX632/prac-workspace/Hello/x86/o-g/Hello_gxx11520.tmp
>/tmp/Hello_g
>> set qnxremotecwd /tmp
>> Warning: /cygdrive/c/QNX632/prac-workspace/Hello/C: No such file or
>directory.
>> Warning: /QNX632/prac-workspace/Hello/.settings: No such file or
>directory.
>> Warning: /cygdrive/c/QNX632/prac-workspace/Hello/C: No such file or
>directory.
>> Warning: /QNX632/prac-workspace/Hello/x86: No such file or directory.
>> Warning: /cygdrive/c/QNX632/prac-workspace/Hello/C: No such file or
>directory.
>> Warning: /QNX632/prac-workspace/Hello/x86/o-g: No such file 
>or directory.
>> MsgNak received - resending
>> MsgNak received - resending
>> MsgNak received - resending
>> Remote exhausted 3 retries.
>> MsgNak received - resending
>> MsgNak received - resending
>> MsgNak received - resending
>> Remote exhausted 3 retries.
>> Remote (spawn error): Exec format error.
>>
>> 5) I cheked the directory "\tmp" on the target, there is 
>only an empty
>file (size 0) "Hello_g".
>> 6) Anything missing when building the OS image?
>>
>> Thanks
>> Weiming
>>
>>
>>     
>>
>> _______________________________________________
>> General
>> http://community.qnx.com/sf/go/post8447
>>   
>
>_______________________________________________
>General
>http://community.qnx.com/sf/go/post8457
>
> 
 
*******************************************
Harman Becker Automotive Systems GmbH
Geschaeftsfuehrung:  Dr. Wolfgang Ptacek  -  Michael Mauser  -  Regis Baudot
Sitz der Gesellschaft: Karlsbad - Registergericht: Mannheim HRB 361395
 
*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat 
sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail
. Das unerlaubte Kopieren sowie die unbefugte...

Weiming Chen

Re: "Spawn error" when using pdebug upon serial to debug programs

Weiming Chen

05/27/2008 9:22 PM

post8496

Re: "Spawn error" when using pdebug upon serial to debug programs

pdebug is in "/proc/boot", and the path is set, so that it can be accessed.

On IDE side, I start up through "Run/Debug...", then choose way of pdebug. See the attached picture.

Weiming

Attachment:

snapshot.JPG 71.97 KB

Elena Laskavaia

05/28/2008 9:59 AM

post8522

Re: "Spawn error" when using pdebug upon serial to debug programs

There are problems with cygwin paths. Can you try new debugger gdb 6.7 
u8 from foundry?

Weiming Chen wrote:
> pdebug is in "/proc/boot", and the path is set, so that it can be
accessed.
>
> On IDE side, I start up through "Run/Debug...", then choose way of pdebug.
See the attached picture.
>
> Weiming
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post8496
>   
>
> ------------------------------------------------------------------------
>

Leonid Khait(deleted)

04/17/2010 1:03 PM

post51977

Re: "Spawn error" when using pdebug upon serial to debug programs

I have the same problems witn IDE 4.6 on Windows XP with serial connection to the target AR91SAM9160-EK with QNX6.4 
Image based on BSP AT91SAM9260.

The serial communication between Host and Target work properly.

On Target I start 

pdebug /dev/ser2,115200

In IDE when I try to debug in Pdebug configuration next errors occure:

Remote target is little-endian
MsgNak received - resending
MsgNak received - resending
MsgNak received - resending
Remote exhausted 3 retries.
Remote was unable to open '/dos/kkt_server_g': Input/output error
MsgNak received - resending
No registers.
info tidlist
Undefined info command: "tidlist".  Try "help info".
set remotebaud 115200
upload C:/ide-4.6-workspace/GMN/kkt_server/arm/o-le-g/kkt_server_gxx51599.tmp /dos/kkt_server_g
set qnxremotecwd /dos
No symbol "qnxremotecwd" in current context.
MsgNak received - resending
Remote exhausted 3 retries.
Remote exhausted 3 retries.
Timed out.
MsgNak received - resending
Remote exhausted 3 retries.
MsgNak received - resending
Remote (spawn error): Permission denied.

Please show the solution.

Elena Laskavaia

04/19/2010 10:00 AM

post52025

RE: "Spawn error" when using pdebug upon serial to debug programs

Can you launch it from default folder (i.e. /tmp)
Looks like remote cwd is failing maybe this cause it not to launch?

-----Original Message-----
From: Leonid Khait [mailto:community-noreply@qnx.com] 
Sent: April 17, 2010 1:03 PM
To: general-ide
Subject: Re: "Spawn error" when using pdebug upon serial to debug
programs

I have the same problems witn IDE 4.6 on Windows XP with serial
connection to the target AR91SAM9160-EK with QNX6.4 Image based on BSP
AT91SAM9260.

The serial communication between Host and Target work properly.

On Target I start 

pdebug /dev/ser2,115200

In IDE when I try to debug in Pdebug configuration next errors occure:

Remote target is little-endian
MsgNak received - resending
MsgNak received - resending
MsgNak received - resending
Remote exhausted 3 retries.
Remote was unable to open '/dos/kkt_server_g': Input/output error MsgNak
received - resending No registers.
info tidlist
Undefined info command: "tidlist".  Try "help info".
set remotebaud 115200
upload
C:/ide-4.6-workspace/GMN/kkt_server/arm/o-le-g/kkt_server_gxx51599.tmp
/dos/kkt_server_g set qnxremotecwd /dos No symbol "qnxremotecwd" in
current context.
MsgNak received - resending
Remote exhausted 3 retries.
Remote exhausted 3 retries.
Timed out.
MsgNak received - resending
Remote exhausted 3 retries.
MsgNak received - resending
Remote (spawn error): Permission denied.

Please show the solution.

_______________________________________________

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

Leonid Khait(deleted)

04/19/2010 11:44 AM

post52041

Re: RE: "Spawn error" when using pdebug upon serial to debug programs

I try  launch from /tmp ( as default ) before too. 
In BSP project /tmp is soft linked to /dev/shmem. And the same problems occure.

The /dos folder I found by mount to Flash Umass strorage drive.

Any time IDE  upload  program to /tmp ( or /dos ) folder with 0 byte lengs.

I tray to debug throug serial line  by pdebug method and  by pppd and qconn too and same problems ( upload file length 
is 0 ).

One thing - the serial line speed was 115200. Is it so importent? 

Any ideas?

 Thank you.

Elena Laskavaia

04/19/2010 11:50 AM

post52042

Re: "Spawn error" when using pdebug upon serial to debug programs

Is there space left on your device? If it cannot upload binary it 
definitely explain problems with debugging.

Leonid Khait wrote:
> I try  launch from /tmp ( as default ) before too. 
> In BSP project /tmp is soft linked to /dev/shmem. And the same problems occure.
>
> The /dos folder I found by mount to Flash Umass strorage drive.
>
> Any time IDE  upload  program to /tmp ( or /dos ) folder with 0 byte lengs.
>
> I tray to debug throug serial line  by pdebug method and  by pppd and qconn too and same problems ( upload file length
 is 0 ).
>
> One thing - the serial line speed was 115200. Is it so importent? 
>
> Any ideas?
>
>  Thank you. 
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post52041
>
>

Leonid Khait(deleted)

04/19/2010 12:03 PM

post52044

Re: "Spawn error" when using pdebug upon serial to debug programs

>Is there space left on your device? 

It was definitely enough amount of space in /tmp or /dos folder.

>If it cannot upload binary it definitely explain problems with debugging.

Are there some other ( not enough  space ) conditios  for succsess upload process? 

Any envirorment variables, libs, .so files in QNX image, etc. ?

Elena Laskavaia

Re: "Spawn error" when using pdebug upon serial to debug programs

Elena Laskavaia

04/19/2010 12:47 PM

post52048

Re: "Spawn error" when using pdebug upon serial to debug programs

This is really weird that file is created but not written.
Can you create a file locally? I.e. using "cat" or something like that?

Leonid Khait wrote:
>> Is there space left on your device? 
>>     
>
> It was definitely enough amount of space in /tmp or /dos folder.
>
>   
>> If it cannot upload binary it definitely explain problems with debugging.
>>     
>
> Are there some other ( not enough  space ) conditios  for succsess upload process? 
>
> Any envirorment variables, libs, .so files in QNX image, etc. ?
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post52044
>
>

David Sarrazin

RE: "Spawn error" when using pdebug upon serial to debug programs

David Sarrazin

04/19/2010 12:54 PM

post52049

RE: "Spawn error" when using pdebug upon serial to debug programs

 

> -----Original Message-----
> From: Leonid Khait [mailto:community-noreply@qnx.com] 
> Sent: April 19, 2010 12:03 PM
> To: general-ide
> Subject: Re: "Spawn error" when using pdebug upon serial to 
> debug programs
> 
> 
> >Is there space left on your device? 
> 
> It was definitely enough amount of space in /tmp or /dos folder.
> 
> >If it cannot upload binary it definitely explain problems 
> with debugging.
> 
> Are there some other ( not enough  space ) conditios  for 
> succsess upload process? 
> 
> Any envirorment variables, libs, .so files in QNX image, etc. ?


/dev/shmem should always allow to write into the file, unless there is
no free RAM in the system.

On the target, what happens if you do 

echo short file > /tmp/foo

Does that create a zero sized file, or an 11 byte file?  If it is a zero
sized file, what is the return value?  You can find this by running
"echo $?" after the command to create the file.


Also, what version of pdebug are you using?  You can check by starting
with -v:

pdebug -v /dev/ser2,115200

> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post52044
> 
>

Leonid Khait(deleted)

04/23/2010 7:40 AM

post52488

Re: RE: "Spawn error" when using pdebug upon serial to debug programs

Sorry my timeout, I was on a distance from the board.

>/dev/shmem should always allow to write into the file, unless there is
>no free RAM in the system.
>On the target, what happens if you do 
>echo short file > /tmp/foo

Yes, /dev/shmem allow to create and write fiiles, the length of file foo after
#echo short file > /tmp/foo is about 11:

# ls -l /tmp
lrwxrwxrwx  1 0         0                10 Apr 23  2010 /tmp -> /dev/shmem
Process 569356 (ls) exited status=0.

# cp /proc/boot/tcpdump /tmp
# ls -l /tmp/tcpdump
-rwxrwxrwx  2 0         0            702941 May 20  2009 /tmp/tcpdump
# 

>Also, what version of pdebug are you using?  You can check by starting
>with -v:
>pdebug -v /dev/ser2,115200

QNX AT91SAM9260-ek target console:

# pdebug -v /dev/ser2,115200
Process 557068 (pdebug) exited status=0.

This version of pdebug was built on May 20 2009.
ProtoVer 0.3
# Com port /dev/ser2 initialized ok.
Target initialized ok.
pdebug initialized

Host resent message with id 9 (0x9). Resending response.
Host resent message with id 4 (0x4). Resending response.
Host resent message with id 4 (0x4). Resending response.
Host resent message with id 5 (0x5). Resending response.
Host resent message with id 7 (0x7). Resending response.

TargetLoad argc=0 envc=0 envv=
cmdline=
stdio=|| || || 

Beg TextToHost 5 /dev/ptyp0
End TextToHost 0 (No error)
Spawn of /tmp/hello_g failed: 8 (Exec format error)

Host resent message with id 8 (0x8). Resending response.



Same time IDE Debug view console:

Remote target is little-endian
MsgNak received - resending
MsgNak received - resending
MsgNak received - resending
Remote exhausted 3 retries.
Remote was unable to open '/tmp/hello_g': Input/output error
MsgNak received - resending
No registers.
info tidlist
Undefined info command: "tidlist".  Try "help info".
set remotebaud 115200
upload C:/ide-4.6-workspace/GMN/hello/arm/o-le-g/hello_g /tmp/hello_g
set qnxremotecwd /tmp
No symbol "qnxremotecwd" in current context.
MsgNak received - resending
Remote exhausted 3 retries.
Remote exhausted 3 retries.
Timed out.
MsgNak received - resending
Remote exhausted 3 retries.
MsgNak received - resending
Remote (spawn error): Exec format error.


So I'm continue on the truble with pdebug from IDE through serial line.
Please help.

P.S. In that system Debuggin through Ethernet and qconn work without problem,
but I need only through serial line.

Elena Laskavaia

04/23/2010 9:10 AM

post52501

Re: RE: "Spawn error" when using pdebug upon serial to debug programs

And you saying after you attempt to launch debugger and it fails, you check /tmp/hello_g  its size is 0?

>upload C:/ide-4.6-workspace/GMN/hello/arm/o-le-g/hello_g /tmp/hello_g

Leonid Khait(deleted)

04/23/2010 9:24 AM

post52508

Re: RE: "Spawn error" when using pdebug upon serial to debug programs

Yes!

This is ARM AT91SAM9260-ek controller with according BSP.

Leonid Khait(deleted)

04/23/2010 9:41 AM

post52513

Re: RE: "Spawn error" when using pdebug upon serial to debug programs

Sorry, this is full issue:

# ls -l /tmp

lrwxrwxrwx  1 0         0                10 Apr 23  2010 /tmp -> /dev/shmem

Process 569356 (ls) exited status=0.

# ls tmp

hello_g

Process 577548 (ls) exited status=0.

# ls /tmp/hello_g

/tmp/hello_g

Process 585740 (ls) exited status=0.

# ls -l /tmp/hello_g

-rwxrwxrwx  3 0         0                 0 Jan 01 00:14 /tmp/hello_g

Process 593932 (ls) exited status=0.

# cp /proc/boot/tcpdump /tmp

Process 602124 (cp) exited status=0.

# ls -l /tmp/tcpdump
-rwxrwxrwx  2 0         0            702941 May 20  2009 /tmp/tcpdump

Process 610316 (ls) exited status=0.

#

Elena Laskavaia

04/23/2010 9:51 AM

post52517

Re: "Spawn error" when using pdebug upon serial to debug programs

Btw with this serial baud rate can you get it working as console? Maybe 
it is wrong rate?

Leonid Khait wrote:
> Sorry, this is full issue:
>
> # ls -l /tmp
>
> lrwxrwxrwx  1 0         0                10 Apr 23  2010 /tmp -> /dev/shmem
>
> Process 569356 (ls) exited status=0.
>
> # ls tmp
>
> hello_g
>
> Process 577548 (ls) exited status=0.
>
> # ls /tmp/hello_g
>
> /tmp/hello_g
>
> Process 585740 (ls) exited status=0.
>
> # ls -l /tmp/hello_g
>
> -rwxrwxrwx  3 0         0                 0 Jan 01 00:14 /tmp/hello_g
>
> Process 593932 (ls) exited status=0.
>
> # cp /proc/boot/tcpdump /tmp
>
> Process 602124 (cp) exited status=0.
>
> # ls -l /tmp/tcpdump
> -rwxrwxrwx  2 0         0            702941 May 20  2009 /tmp/tcpdump
>
> Process 610316 (ls) exited status=0.
>
> # 
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post52513
>
>

Leonid Khait(deleted)

04/23/2010 10:35 AM

post52531

Re: "Spawn error" when using pdebug upon serial to debug programs

I can workin on console without any problems on 115200.

Sorry, I'll try and report on 57600 on sanday.

Leonid Khait(deleted)

04/25/2010 9:07 AM

post52655

Re: "Spawn error" when using pdebug upon serial to debug programs

On serial speed 57600 I have the same problems.

Elena Laskavaia

04/26/2010 10:27 AM

post52770

Re: "Spawn error" when using pdebug upon serial to debug programs

Can you try lower rates?

Leonid Khait wrote:
> On serial speed 57600 I have the same problems.
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post52655
>
>

David Cummings(deleted)

04/26/2010 10:51 AM

post52781

Re: "Spawn error" when using pdebug upon serial to debug programs

The issues I've seen in the past with pdebug all relate to a baud rate set too high, or mismatched between the host and 
the target.

When you tried the lower baud rate, did you change it in the IDE AND in the launch of pdebug? (http://www.qnx.com/
developers/docs/6.3.0SP3/neutrino/utilities/p/pdebug.html)

The pdebug use message also states that pdebug should not be launched with a baud rate higher than 57600:

>use pdebug
<snip>
  /device_name[,baud]   Open and use the specified device, such as
                        /dev/ser1, optionally setting the baud rate.
                      **baud rates higher than 57600 NOT recommended**
<snip>

> Can you try lower rates?
> 
> Leonid Khait wrote:
> > On serial speed 57600 I have the same problems.
> >
> >
> >
> > _______________________________________________
> >
> > General
> > http://community.qnx.com/sf/go/post52655
> >
> >

Leonid Khait(deleted)

04/26/2010 12:44 PM

post52794

Re: "Spawn error" when using pdebug upon serial to debug programs

Please get me more info about cygwin configuration in Windows XP.

On my PC  I found some older ( before QNX IDE installation ) 
cygwinccompiler.pyc program in C:\IBMTOOLS\Python22\Lib\distutils folder and
also some descriptions in Windows registryr:

HCEY_LOCAL_MACHINE
 -SOFTWARE
    -Cygnus Solutions
        -Cygwin
          -Mounts V2
            /                                     c:\cygwin
            /usr/bin                          c:\cygwin/bin
            /usr/lib                            c:\cygwin/lib  

Some time ago I  create c:\cygwin directory for IDE properly work.

So have I create now c:\cygwin\bin and  c:\cygwin\lib  folders too 
or
I need to clean all cygwin key descriptions from Windows HKEY_LOCAL_MACHINE and HKEY_LOCAL_USER registry?

Leonid Khait(deleted)

05/01/2010 10:55 AM

post53367

Re: "Spawn error" when using pdebug upon serial to debug programs

At me the problem proceeds. 

Has tested the same Host PC with IDE for communications with PC x86 with QNX Momentics through COM-port. Debugging both 
through pdebug, and through PPP connection - qconn work normally.

As soon as I am switched HOST on AT91SAM9260-ek + BSP with same  COM-port communication tools debugging both through 
pdebug, and through PPP-qconn does not work. 

Thero length debuging program file in /tmp->/dev/shmem problem occures.

And same time debugging through Ethernet-qconn works normally.

P.S. 
On Host - PC with IDE I use Prolific USB-> COM the adapter.

Leonid Khait(deleted)

Re: "Spawn error" when using pdebug upon serial to debug programs

Leonid Khait(deleted)

05/07/2010 8:16 AM

post53743

Re: "Spawn error" when using pdebug upon serial to debug programs

Please show me  the path on pdebug sources for problem of "pdebug serial" studying.

Return

The text you entered is not a valid object ID
More Information
Object IDs begin with an object prefix and end with a number. For example, if you enter
artf2345
the application will jump directly to an artifact with the ID artf2345. Some valid object prefixes are:
artf	for an artifact
doc	for a document
page	for a project page
topc	for a discussion topic
wiki	for a wiki page