Thread: [Pydev-users] [pydev - Users] helpin debug mode strings are cut
Brought to you by:
fabioz
From: SourceForge.net <no...@so...> - 2007-09-26 08:40:59
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4537866 By: nookieman Hi there, i'm currently debugging a program and it's especially interesting for me what the content of a long string variable is at a given time. The problem i encountered is that the content of variables are cut at a certain point so im not able to read its content. Is there some configuration that sets the length that is displayed? Or some other workaround to be able to see the complete content of the variable? thanks chriz ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 |
From: SourceForge.net <no...@so...> - 2007-09-26 10:32:25
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4538015 By: fabioz Not currently... there's a bug for that already at: https://sourceforge.net/tracker/index.php?func=detail&aid=1788406&group_id=85796 &atid=577329 You can as workarounds use pydev extensions (where you can inspect things from the console using prints) or you can go to eclipse/plugins/org.python.pydev.debug/pysrc/pydevd_vars.py and change that limit manually (line 131: varToXml()): if len(value) > 200: ....value = value[0:200] ....value += '...' Just put a higher value there. Note that this could make your communication with the debugger somewhat slower (specially if you're dealing with large strings) and could lead to the bug related at: https://sourceforge.net/tracker/index.php?func=detail&aid=1788409&group_id=8 5796&atid=577329 (where variables dissapear because of the timeout specified to the debugger server). Cheers, Fabio ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 |
From: patrimith <pad...@gm...> - 2007-09-26 14:55:54
|
SourceForge.net wrote: > > You can as workarounds use pydev extensions (where you can inspect things > from > the console using prints) > You can only doing this when debugging code that is running within Eclipse and not when using the remote debugger, right? Thanks, Patrick Smith -- View this message in context: http://www.nabble.com/-pydev---Users--helpin-debug-mode-strings-are-cut-tf4520837.html#a12902760 Sent from the pydev-users mailing list archive at Nabble.com. |
From: Fabio Z. <fa...@gm...> - 2007-09-26 16:17:31
|
> > > You can as workarounds use pydev extensions (where you can inspect > things > > from > > the console using prints) > > > > You can only doing this when debugging code that is running within Eclipse > and not when using the remote debugger, right? > Actually, you can... if you do the settrace in the remote machine passing that you want the stdout and stderr to be redirected to the server (eclipse): pydev.settrace(host='xxx', stdoutToServer=True, stderrToServer=True) Cheers, Fabio |