/*:
There seems to be a bug in gdb which causes it to not stop at certain
breakpoints. It occurs with C++ sources compiled with gcc3-3.02,
but not when
gcc2-2.96 is used. All gdb versions I tried (ver 5.0rh-15 and
5.1.0.1) had
the same problem.
I'm suspecting there may be newer versions around
bug-gdb´ÔÀÇ ¸ÞÀÏÁÖ¼Ò´Â http://sources.redhat.com/ml/bug-gdb/2001-12 À¥ÆäÀÌÁö¿¡¼
°Ë»ö/¼öÁýµÈ ÀÚ·áÀ̹ǷΠÀüÀÚ¿ìÆí Á¤º¸ÀÌ¿Ü¿¡
¾î¶°ÇÑ Á¤º¸µµ ¾øÀ½À» ¾Ë·Áµå¸³´Ï´Ù.
ÀÌ ¸ÞÀÏÀÇ ¼ö½ÅÀ» ¿øÄ¡ ¾ÊÀ¸½Ã¸é Click
¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë
bug-gdb´Ô
¾È³çÇϼ¼¿ä?
ÀúÈñ´Â
Àüȸ¦ ÀÌ¿ëÇؼ
°»ç¿Í 1 : 1 ·Î ¿Ü
Title: Á¦¸ñ¾øÀ½
¾È³çÇϼ¼¿ä.±âÇÁÆ®³ª¶óÀÔ´Ï´Ù
Çã¶ô¾øÀÌ ±ÛÀ» ¿Ã¸®°Ô µÇ¾î
ÁË¼Û ÇÕ´Ï´Ù.
Á¦Ç° Á¦Á¶»ç¿ÍÀÇ Á÷°Å·¡ À¯ÅëÀ» ÅëÇÏ¿©
Àú·ÅÇÑ ´Ü°¡·Î
´Ù¾çÇÑ Á¦Ç°À» ÆǸÅÇÏ°íÀÚ ÇÏ¿À´Ï ±âŸ ±Ã±ÝÇϽÅ
Á¡À» ¹®ÀÇÇÏ¿© Áֽøé ÃÖ¼±À» ´ÙÇÏ¿© ´äÇص帮°Ú½À´Ï´Ù.
¿ëµµ:
Title: Subscribe FREE!!
PassivePROFITS
Residual Wealth Made Easy
Title: Subscribe FREE!!
PassivePROFITS
Residual Wealth Made Easy
)
±¸¸Û
¡Þ ÏÞ(ªÛ)ªë
ÆÄ´Ù
¡Þ ª¦ªÁªÎ~
¿ì¸®(Áý)~
¡Þ ÐÝåà(ªªóª®ªç)
±ÝºØ¾î
¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë
bug-gdb´Ô
¾È³çÇÏ
to
see where it's going astray...
Kevin
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
Title: Subscribe FREE!!
PassivePROFITS
Residual Wealth Made Easy
Hi!
I _also_ found the the thread/float/NaN bug in GDB. But Kevin Buettner
beat me in supplying the patch... I saw Kevin's message while I was
preparing this message. How funny/strange two people find the same bug
at the same moment when it's been there for half a year...
But I am not sending
circumstances under which it
doesn't work so that this problem can be fixed.
Thanks,
Kevin
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
... It is CPU related. But how?!
Bart,
If you have the time, I think it'd be worth tracking this problem
down...
Kevin
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
))
return signals[sig].name;
else
return signals[TARGET_SIGNAL_UNKNOWN].name;
}
Petr Ledvina
[EMAIL PROTECTED]
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
Hello GDB Bug -
I am using GDB 4.16 (sparc-sun-solaris2.5).
-
If I put the following code in the file odd.cc and compile
it with the command gcc -v -g -o odd odd.cc, it is compiled OK
and part of the verbiage it spews out while compiling is
/depot/gnu/plat/lib/gcc-lib/sparc-sun
I seem to have found a problem with thread handling in version 5.0 (see show version
below.
Could you tell me if this a bug or something which I can control and work around? I
would like
to just get to my breakpoint and that doesn't seem possible.
Thank you,
Joel Breazeale
-- transcript
¹öÁö ȸ»ç¿¡¼ ÀÏÇÏ°í ÀÖ½À´Ï´Ù.
¡Þ úüð©(ªªçª¦ªÀª¤) ÇüÁ¦
¡Þ ªÏª¿ªéª¯ ÀÏÇÏ´Ù
¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë¡ë
bug
Hello,
I'm running SuSE-7.3 and gdb 5.0 configured as i686-pc-linux-gnu.
I have attached a report of a possible bug with gdb.
The gdb output shows that running a program for the first time
works. For on subsequent runs it fails. Outside of gdb the program
works fine any time it is run.
Any
PROTECTED]
God bless America. And shed His Grace on thee.
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
)
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
A note that the gdb doesn't always compile on a
HPUX, as (I think this is what is going on) the configure script detects 64bit
hardware, but HP may not have included the 64bit linker (probably unless you pay
for it, at any rate we only had the 32 bit linker). I has to ensure configure
/libpthread.so.0 - libpthread-0.9.so*
gcc -v
Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux/2.96/specs
gcc version 2.96 2731 (Linux-Mandrake 8.0 2.96-0.48mdk)
--jeff koftinoff
[EMAIL PROTECTED]
___
Bug-gdb mailing list
[EMAIL PROTECTED
Title: Untitled Document
Áö¿ªÀ» °ü¸®ÇÏ½Ç ÁÖºÎÆÀÀåÀ»
ÃʺùÇÕ´Ï´Ù !
´ç»ç´Â ±èÄ¡³ÃÀå°í Àü¹®À¯Åë¾÷ü·Î¼
°¢ Áö¿ªÀ» °ü¸®ÇÏ½Ç ÁÖºÎÆÀÀå´ÔÀ» ¸ð½Ê´Ï´Ù
Title: FW: Unsupported feature or bug?
-Original Message-
From: Gvozdeva, Svetlana
Sent: Tuesday, September 11, 2001 4:01 PM
To: '[EMAIL PROTECTED]'
Subject: FW: Unsupported feature or bug?
-Original Message-
From: Gvozdeva, Svetlana
Sent: Tuesday
snaps are comming from the
unreleased 5.1 branch.
Andrew.
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
the data to
the wrong location in memory (see below).
This is an ancient version of GDB. You can get a newer one from
sources.redhat.com, or from any GNU mirror.
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
Áֽñ⠹ٶø´Ï´Ù.ȸ½ÅÇØ ÁÖ½Ã¸é ¹Ù·Î
Á¶Ä¡Çϵµ·Ï ÇÏ°Ú½À´Ï´Ù.º» ¸ÞÀÏÀº À¥¼ÇÎ µµÁß bug-gdb´ÔÀÇ
¸ÞÀÏÀ» º¸°í º¸³»µå¸³´Ï´Ù.°³ÀÎÁ¤º¸ º¸È£ ´ã´çÀÚ : ±èÈ«ÁÖ¿¬¶ôó
: 017-406-4865À̸ÞÀÏ [EMAIL PROTECTED
¿¡
ÀǰŠǥ½Ã´õ ÀÌ»ó ¸ÞÀϼö½ÅÀ»
¿øÇÏÁö ¾ÊÀ¸½Ã¸é ȸ½ÅÇØ Áֽñ⠹ٶø´Ï´Ù.ȸ½ÅÇØ ÁÖ½Ã¸é ¹Ù·Î
Á¶Ä¡Çϵµ·Ï ÇÏ°Ú½À´Ï´Ù.º» ¸ÞÀÏÀº À¥¼ÇÎ µµÁß bug-gdb´ÔÀÇ
¸ÞÀÏÀ» º¸°í º¸³»µå¸³´Ï´Ù.°³ÀÎÁ¤º¸ º¸È£ ´ã´çÀÚ : ±èÈ«ÁÖ¿¬¶ôó
: 017
Title: ¾ÆÀ̱èõ(igimcheon) ±¤°í¿ë ¸ÞÀÏ
ÀÌ ¸ÞÀÏ·ÎÀÎÇØ º»ÀÇ ¾Æ´Ï°Ô Æó¸¦ ³¢Ãļ ´ë´ÜÈ÷ Á˼ÛÇÕ´Ï´Ù.
ÀÌ ¸ÞÀÏÀº ÀúÈñ°¡ ÀÎÅÍ³Ý ¼ÇÎÁß¿¡
http://www.kr.gnu.org/manual/gdb/html_mono/gdb.html¿¡¼ bug-gdb´ÔÀÇ [EMAIL PROTECTED]À» ã¾Æ¼ º¸³»µå¸®´Â °ÍÀÔ´Ï´Ù.
µû¶ó¼ ±ÍÇϲ²¼ ÀÌ ¸ÞÀÏÀ» ¼ö½Å°ÅºÎ¸¦ ¿øÇϽÃ
guys
i have found a bug in gdb.
i am using Win95 version 4.00.950 with 32 mb ram. i am
using mingw32 compiler
2.95.2 19991024 (release). my processor is Intel
Pentium II 350 mhz.
GDB version 4.18
this is what happened:
i fired up my gdb. and wanted to see what commands are
available. so i
I'm trying to debug kernel module on remote PPC machine.
Say me if I'm doing something wrong.
I had fonud 0xc303b04c address using loadmodule.sh script
Please answer to [EMAIL PROTECTED] too.
==
Copyright 2000 Free Software
a compilation unit that contains this offset.
Any other ideas?
Thanks
Tim
[EMAIL PROTECTED]
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
Wright
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
Hi,
The following change in 'sim/v850' added a serious bug, not removed any ;-)
- a clip from 'sim/v850/ChangeLog' ---
2001-01-31 Jonathan Larmour [EMAIL PROTECTED]
* Makefile.in (gencode): Link with libopcodes in build tree rather
than
**
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
Ŭ¸¯ÇϽŠÈÄ °ÀÇ ½Åû¶õ¿¡
Àִ½ùü°ÀÇ ½Åû ÆûÀ» ÀÛ¼ºÇϼż º¸³» ÁÖ½Ã¸é µË´Ï´Ù.¹°·Ð, ÀüÈ 02-588-0510 À¸·Îµµ ½ÅûÇÏ½Ç ¼ö ÀÖ±¸¿ä.
¾Æ¹«ÂÉ·Ï ÀÌ ÇнÀ¹ýÀÌ bug-gdb´ÔÀÇ È¸È ½Ç·Â Çâ»ó¿¡ ÀÛÀº º¸ÅÆÀÌ µÇ¾úÀ¸¸é
ÇÕ´Ï´Ù.
bug-gdb´Ô²²´Â http://www.kr.gnu.org/prep/mailinglists.html¿¡ ÀÖ´Â ÁÖ¼Ò¸¦ º¸°í ¸ÞÀ
Ŭ¸¯ÇϽŠÈÄ °ÀÇ ½Åû¶õ¿¡
Àִ½ùü°ÀÇ ½Åû ÆûÀ» ÀÛ¼ºÇϼż º¸³» ÁÖ½Ã¸é µË´Ï´Ù.¹°·Ð, ÀüÈ 02-588-0510 À¸·Îµµ ½ÅûÇÏ½Ç ¼ö ÀÖ±¸¿ä.
¾Æ¹«ÂÉ·Ï ÀÌ ÇнÀ¹ýÀÌ bug-gdb´ÔÀÇ È¸È ½Ç·Â Çâ»ó¿¡ ÀÛÀº º¸ÅÆÀÌ µÇ¾úÀ¸¸é
ÇÕ´Ï´Ù.
bug-gdb´Ô²²´Â http://gnu1.mirror.or.kr:80/manual/gdb/html_node/gdb_152.html¿¡ ÀÖ´Â Á
The following bug can be reproduced with gdb 5.0 and gcc 2.95.2 running
under Solaris 2.6.
Compile the enclosed files with
g++ -g *cc
and run
gdb a.out
Inside gdb, do a
print cs::constants::dbDirEnvVarName
and you get
no symbol cs in current context
?
Sincerely,
Kalonji Kabongo
Omgeo
voice: 617-856-2781
cellphone: 617-594-4227
email: [EMAIL PROTECTED]
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
On Apr 15, 12:59pm, Willy Jacobs wrote:
This is the change I made (i386-nat.o added):
Thanks. I checked in a patch nearly identical to yours last Thursday.
See http://sources.redhat.com/ml/gdb-patches/2001-04/msg00119.html.
Kevin
___
Bug-gdb
--
Willy Jacobs
mailto:[EMAIL PROTECTED]
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
Attached is a sample program illustrating gdb cannot
understand the enumerated type when the most significant
bit is set, resulting in a 'negative' value for the enumeration.
From what I know, the enumerated types work perfectly
during execution time and it's only when we're examining
these
.
pramod
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
This has got to be a bug!
gdb 5.0 configured as "i586-pc-linux-gnu".
For (but with default constructors)
class base{public: int i;};
class dervied: public base{public: int j;};
base* unknown = new derived();
Using gdb and 'print *(derived*)unknown' gives
incorrect/random values
to [EMAIL PROTECTED]
Hi,
I have thought/remember
that it was possible to invoke some library functions
under gdb
(see below).
For 4.18 this feature does NOT work.
Is it a feature or a bug ?
Best regards,
Julian
(gdb) p s2
$1 = 0x221a8 "/vidtool1 / Calroot / Cala
any fashion is much more so.
FEEDBACK:
-
I don't expect any feedback on this problem. It happens rarely, but since
it seems to be a legitimate bug, I thought I'd send it in. I'm not sure
how much else I can add to what's here, but if necessary, I will try.
Oh, and thanks for GDB; I've u
John Hughes wrote:
so we realy have:
if (! (long long )( len ) = 4 )
return 0;
Spot the missing parens!
Thanks. I've committed the attatched (and overcompensated in the
process :-)
Andrew
Fri Jan 19 02:31:40 2001 Andrew Cagney
Title: Untitled Document
bug-gdb´Ô ¾È³çÇϼ¼¿ä? gnu.org¿¡¼ bug-gdb´ÔÀÇ ¾ÆÀ̵𸦠º¸°í ½Å³âÀλç
µå¸³´Ï´Ù. »õÇØ¿¡ ±â¿øÇϽô ¸ðµçÀÏÀÌ·ç¾î Áö½Ã±æ ¹Ù·Î°í¿ä. ½¬´Â½Ã°£,¿Ü·Î¿ï¶§ "½ß¼î"°¡ ÇÔ²²ÇÔÀ» ÀØÁö
'
Since I haven't hand-modified any makefiles, would this be some kind of
bug? What other data would be required to further diagnose this? Full
configure and build logs? Software versions?
Moreover, is there some quick fix I can make so that the build can
finish? I'd really like to use
--Gary Parnes
[EMAIL PROTECTED]
_______
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
̶õ ¶æÀÌ¿¡¿ä.
A: ¸Þ¸®¾È°ú ¾àÈ¥ÇÑ´Ù°í µé¾ú´Âµ¥.B: »ç½Ç ÀÌ¹Ì Çß¾î.A: ¾î,
Á¤¸»À̾ß? ±×·¡,¾àÈ¥½ÄÇÑ ±×³¯ ¹ã¿¡ ±âºÐÀÌ ¾î¶®¾î?B: ¼¼»óÀ» ¾òÀº ±âºÐÀ̾úÁö.
¢Ä ¿À´ÃÀÇ ÀϾî ÇѸ¶µð ¢Å
¡ØÀϾ ¿µ¾î¿Í °°Àº ÇüÅ·Π±¸¼º µÇ¾î
ÀÖ½À´Ï´Ù.bug-gdb´Ô
¾È³ç
GNU gdb 5.0
...
This GDB was configured as "i586-sco-sysv5uw7.1.1".
In breakpoint.c we see:
if (!TARGET_REGION_OK_FOR_HW_WATCHPOINT (vaddr, len))
return 0;
But TARGET_REGION_OK_FOR_HW_WATCHPOINT is defined by:
#if
Hello!
There is a small typo in gdb/remote.c that causes the command
show remotewritesize
to act like
set remotewritesize
The bug is in _initialize_remote(), just search for "remotewritesize". The
first occurrence in add_cmd() is correct, the second one s
t;opcode/vax.h"
+#include "frame.h"
/* Vax instructions are never longer than this. */
#define MAXLEN 62
Regards,
V.B.
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
at machinasapiens dot com
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
uit
The program is running. Exit anyway? (y or n) y
/mnt3/jlp
--
Peter Schauer [EMAIL PROTECTED]
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
dow system.)
_______
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
e Sarrazin [EMAIL PROTECTED]
_______
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
Yes. Use Xnest which gives you a X server which runs inside your host X server.
So the procedure is something like this:
Xnest :1
PROTECTED]
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
_______
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
a much better shot than one which has explicit
knowledge about the X Window system.)
Isn't that the 'commands' command?
-- Benoît
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
called `clear_xgrab' was
created, this would do what the original posted wanted.
(I still think it's better to use two machines to do this type of
debugging though.)
Kevin
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug
[EMAIL PROTECTED] writes:
Sent via Deja.com http://www.deja.com/
Before you buy.
Iam using gdb 5.0. Is there a version after this ?
I've made numerous C++ fixes since then, try the CVS gdb.
Well, actually, wait a week, then try it.
--Dan
hi,
Whenever I use gdb as mortal user, I get the following error:
stroessl@mantrasun1:~/3Gamik/bingdb Hippo
GNU gdb 4.18
[snip]
This GDB was configured as "sparc-sun-solaris2.7"...
(gdb) b main
Breakpoint 1 at 0x24e38: file main.c, line 44.
(gdb) r
Starting program:
I have encountered what looks like a bug under gdb 5.0.
The bug appears when debugging a multi-threaded program under
Linux RedHat 6.2 (x86). It looks as if gdb does not know how to
continue
out of a thread that has finished(terminated/exited). This particular
problem
did not occur with an old
Regis ALTMAYER wrote:
Hi.
Here is a problem I noticed using gdb on two SOLARIS Intel plateforms (uname -a:
SunOS pcxlg6 5.7 Generic_106542-08 i86pc i386 i86pc), with two different backgrounds:
Background1:
gcc -v :
Reading specs from /usr/local/lib/gcc-lib/i386-pc-solaris2.6/2.8.1/specs
Hello bug-gdb,
When I try make gdb-5.0 beta for --target=mips-idt-ecoff
i see next messages:
gcc -c -DHAVE_CONFIG_H -I. -I. -I/usr/local/include -DRL_LIBRARY_VERSION='"4.0"' -g
-O2 histsearch.c
rm -f shell.o
gcc -c -DHAVE_CONFIG_H -I. -I. -I/usr/loc
cate large
chunks of memory. In our production system in-house, we see errors
like this pretty often.
Has anyone reported errors like this yet? We'd be willing to help in
any way for this bug to be fixed. If you'd like me to build a debug
version of gdb and give you information, let me know.
Hello!
I've been working with the GUI version GDB built from ecosSWtools-990319 src
for a period of time. ecosSWtools is an useful tool kit and I have especial
interest in the DIR src/gdb/mswin. I'd like to know when it will be
upgraded. Could you tell me?
I encountered a few bugs. They may be
Dear Guy,
I installed gdb-5.0 and confirmed the bug is fixed in this version.
Thank you.
Tak
From: Guy Harris [EMAIL PROTECTED]
Date: Fri, 9 Jun 2000 15:43:33 -0700 (PDT)
CC: [EMAIL PROTECTED]
X-Mailer: ELM [version 2.4ME++ PL59 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset
Hi, people.
I think I found a bug in gdb, and want to know if it is a known bug
and if there is any patch for it.
The version of my gdb is:
GNU gdb 4.17
Copyright 1998 Free Software Foundation, Inc.
skip
This GDB was configured as "sparc-sun-solaris2.5.1".
Following is the bug
Original Message
Subject: THIS is not a BUG but an HELP request
Date: Fri, 26 May 2000 23:50:45 +0200
From: Paolo Valota [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Hello,
Could I have some information about this new strtab??
__pp1:T(14,1)=s227__PP1a:(0,1),0,32;__PP1d:(14,2
I have reported and traced down problem with setting (resetting) breakpoints in
shared libraries earlier.
The problem exists in 4.18 but also in 5.0.
The problem occurs when you do a debug session and rerun the session. All
dynamically loaded libraries will be unloaded upon rerun, set
Your e-mail address: [EMAIL PROTECTED]
appears in the Free On-line Dictionary
of Computing in the following entries:
http://foldoc.doc.ic.ac.uk/?GDB
Please mail me if you want your address removed or have any
other comments. Please *do not* reply just to say it's OK.
I will not contact
I agree, your print statement should work.
I get the same mesage and unfortanately have no idea how to get around it.
The documentation indicates to me that the print statement should work.
"Chih-Wei(Jim) Chang" wrote:
Hi,
Sorry if this is not a bug. But this is something
101 - 173 of 173 matches
Mail list logo
