lillo: Profiler
lillo: Profiler
Lillo:
As there seems to be no private messages here I report it to the forum:
The profiler in version 0.14 continues not creating the report if a filename is passed in the command$ list.If the command$ is left empty it works.
The same bug you could not reproduce in v 0.13. Perhaps if I send you my PC via DHL.....
AS I said before, it's not important as I can use the preprocessor to compile an alternate version for profiling.
BTW: The 0.13 profiler created an exe 0f 300K, 4 times biggerthan the normal exe.The 0.14 profiler creates a 3,2Meg exe, you may be using tons of (faster) static vars!!
As there seems to be no private messages here I report it to the forum:
The profiler in version 0.14 continues not creating the report if a filename is passed in the command$ list.If the command$ is left empty it works.
The same bug you could not reproduce in v 0.13. Perhaps if I send you my PC via DHL.....
AS I said before, it's not important as I can use the preprocessor to compile an alternate version for profiling.
BTW: The 0.13 profiler created an exe 0f 300K, 4 times biggerthan the normal exe.The 0.14 profiler creates a 3,2Meg exe, you may be using tons of (faster) static vars!!
Not full support yet, include files aren't working (GDB gets nuts because the main function overlapping the other ones, what can't happen in C), dynamic arrays won't show their contents (i can't get GDB to use Fortran arrays), enum's will be converted to integers, but everything else seems to be working..
Btw, you have to type the var names in UPPERCASE to watch them, if they aren't parameters or local vars, that are watched automatically.
Insight for Windows can be download from the Cygwin (the gdb package).
Btw, you have to type the var names in UPPERCASE to watch them, if they aren't parameters or local vars, that are watched automatically.
Insight for Windows can be download from the Cygwin (the gdb package).
Compiling with profiling support is completely independent of compiling with debugging support... So you can compile with the -profile switch and still not use -g, as well as you could use both, resulting in a profiling exe with debug support ;)
Anyway, I can't reproduce your problem either; here's what I do:
Having this small program:
I compile it with
Then if I run command.exe with:
I still get profile.txt generated in the directory of the exe...
Anyway, I can't reproduce your problem either; here's what I do:
Having this small program:
Code: Select all
f$ = command$
print "hello"
sleep
Code: Select all
fbc command.bas -profile
Code: Select all
command.exe these are fake arguments
No, it's not ANY command line, I'm afraid i did'nt explain it very well.
It's dragging & dropping a file to the exe (that should convert to a command line parameter surrounded by doublequotes in windows)
Of course, my program is prepartre do strip the doublequotes when it receives them.
If the file name is written manually in a command line, profiler works.
Yes -g is not needed, but it was in v0.13 (unless I got puzzled with the d'n'd' problem)
It's dragging & dropping a file to the exe (that should convert to a command line parameter surrounded by doublequotes in windows)
Of course, my program is prepartre do strip the doublequotes when it receives them.
If the file name is written manually in a command line, profiler works.
Yes -g is not needed, but it was in v0.13 (unless I got puzzled with the d'n'd' problem)
-
- Posts: 1706
- Joined: May 27, 2005 6:34
- Location: Cambodia, Thailand, Lao, Ireland etc.
- Contact:
Hi:Antoni wrote:No, it's not ANY command line, I'm afraid i did'nt explain it very well.
It's dragging & dropping a file to the exe
<snip>
What happens is the “profile.txt” file is created in the current directory, which is not necessarily the directory of the exe, so it is easy to get “lost”. In my tests when I drag-and-drop a file on the exe the “profile.txt” ends up in C:\Documents and Settings\XXX where XXX is the current user.
Now that I look, there is a lot of old garbage in this directory.
Have fun
Garvan
I should have guessed it....Drag and drop leads to strange current paths with nothing to do with the Dragged or the dropped items. I'm adding
in all the bach files I intend to use with drag and drop...
Lillo: excuse me for not delimiting the problem and waste your time.
Code: Select all
cd /d %~dp0
Lillo: excuse me for not delimiting the problem and waste your time.