This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 177442

Summary: Can not debug a remote project in localized path with smart secure copy
Product: cnd Reporter: Alexander Pepin <apepin>
Component: DebuggerAssignee: Vladimir Voskresensky <vv159170>
Status: VERIFIED FIXED    
Severity: normal CC: jf4jbug, susanm
Priority: P1 Keywords: I18N
Version: 6.x   
Hardware: PC   
OS: Windows Vista   
Issue Type: DEFECT Exception Reporter:
Attachments: gdb log
gdb log in Japanese Windows
gdb log in Ubuntu 9.04 (ja_JP.UTF-8 locale)
track encoding

Description Alexander Pepin 2009-11-23 08:15:34 UTC
Created attachment 91539 [details]
gdb log

Now we can build and run remote projects locally created in 'localized' directories but we can not debug such projects. To be consistent we should resolve that issue as well.

Steps to reproduce:
- add solaris remote host using Secure Copy synchronization type and GNU tool collection
- create Quote sample in localized directory
- clean and build it
- do step into
Result: "Application failed to start" and "Gdb could not load your program. Terminating debug session." Information windows appear.
Comment 1 Keiichi Oono 2009-11-24 04:19:29 UTC
Created attachment 91588 [details]
gdb log in Japanese Windows

I've reproduced in Japanese Windows.
 * local host: Japanese Windows XP
 * local user's runtime default encoding: Shift_JIS
 * remote host: OpenSolaris 2009.06
 * remote user's runtime default encoding: UTF-8

The project directory with Japanese characters can not be found, and executable "quote_1" can not be executed.
Comment 2 Keiichi Oono 2009-11-24 04:26:49 UTC
Created attachment 91589 [details]
gdb log in Ubuntu 9.04 (ja_JP.UTF-8 locale)

I've also tested in Ubuntu 9.04 (ja_JP.UTF-8 locale), and behavior is different from Windows environment.
 * local host: Ubuntu 9.04
 * local user's runtime default encoding: UTF-8
 * remote host: OpenSolaris 2009.06
 * remote user's runtime default encoding: UTF-8

The project directory can be found, and executable "quote_1" is executed. However, breakpoint does not work.
Comment 3 Keiichi Oono 2009-11-24 04:28:34 UTC
Add I18N keyword
Comment 4 Keiichi Oono 2009-11-24 04:32:14 UTC
I guess encoding mismatch causes an error to execute target executable files. However, I also think, to debug in remote host with different encoding from local host, is not typical case.
Comment 5 Vladimir Voskresensky 2009-11-24 07:05:27 UTC
Created attachment 91602 [details]
track encoding

track encoding of strings used inside GDB based on ExecEnv of run gdb
Comment 6 Vladimir Voskresensky 2009-11-24 10:17:26 UTC
fixed in trunk:
http://hg.netbeans.org/cnd-main/rev/ce37649bf359
Comment 7 Egor Ushakov 2009-11-24 10:21:36 UTC
fix reviewed
Comment 8 Alexander Pepin 2009-11-25 05:07:00 UTC
The bug is generally fixed.
Remaining issues:
- attach to remote project causes appearing "information" window with text "The executable associated with the selected project does not match the selected ID." but that does not break the debugging process.
- if the project is created in localized directory without space (localized "MyDocuments" instead of "My Documents") then breakpoints do not work.

I think we should integrate the fix into release68 clone and make release notes and recommend users not to use localized directories or project names for remote projects.
Comment 9 Vladimir Voskresensky 2009-11-25 08:43:59 UTC
integrated into release68:
http://hg.netbeans.org/release68/rev/d7162cddfd8c
Comment 10 Quality Engineering 2009-11-25 16:58:37 UTC
Integrated into 'main-golden', will be available in build *200911251400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/ce37649bf359
User: Vladimir Voskresensky <vv159170@netbeans.org>
Log: fixed IZ#177442 -  Can not debug a remote project in localized path with smart secure copy
Comment 11 Alexander Pepin 2009-11-26 10:23:21 UTC
verified in RC1 candidate