On 20 Mar 2009, at 19:54, Paul Ishenin wrote:
Jonas Maebe wrote:
In trunk/r12933 you can now force the compiler to always store
absolute path for include files using -gostabsabsincludes. See the
svn comment for why it's not the default (gcc also never does this,
you can't even force it
Jonas Maebe wrote:
Sorry, for me it is somehow strange that this works different:
{file=C:/programming/fpc/rtl/i386/i386.inc,fullname=C:/programming/fpc/rtl/i386/i386.inc}
and
{file=./include/messagedialogs.inc}
main unit file is located in
C:/programming/mytest/0.9.27/SafeCall/project1.lpr
On 21 Mar 2009, at 15:07, Paul Ishenin wrote:
Jonas Maebe wrote:
Sorry, for me it is somehow strange that this works different:
{file=C:/programming/fpc/rtl/i386/i386.inc,fullname=C:/
programming/fpc/rtl/i386/i386.inc} and
{file=./include/messagedialogs.inc}
main unit file is located in
Paul Ishenin wrote:
Thanks to Jonas. We don't need to write so big debug paths anymore. He
successfully fixed an issue with path in the stabs in r12812.
Jonas, can you look futher. I pasted one example here (executed
-file-list-exec-source-files)
On 20 Mar 2009, at 17:52, Paul Ishenin wrote:
Paul Ishenin wrote:
Thanks to Jonas. We don't need to write so big debug paths anymore.
He successfully fixed an issue with path in the stabs in r12812.
Jonas, can you look futher. I pasted one example here (executed -
Jonas Maebe wrote:
In trunk/r12933 you can now force the compiler to always store
absolute path for include files using -gostabsabsincludes. See the svn
comment for why it's not the default (gcc also never does this, you
can't even force it to do that). There is no way to specify a separate
On Friday 27 February 2009 15:17:29 Paul Ishenin wrote:
How this solved by mseide developers?
MSEgui uses includefiles for headers in platform specific units
(msesysintf.pas, mseguiintf.pas) only, so there are not many include files in
the MSEgui framework and the names are unique.
In order to
On Sat, 28 Feb 2009 09:57:05 +0100
Martin Schreiber fp...@bluewin.ch wrote:
On Friday 27 February 2009 15:17:29 Paul Ishenin wrote:
How this solved by mseide developers?
MSEgui uses includefiles for headers in platform specific units
(msesysintf.pas, mseguiintf.pas) only, so there are not
On Saturday 28 February 2009 11:07:48 Mattias Gaertner wrote:
On Sat, 28 Feb 2009 09:57:05 +0100
And how does MSEGui find lists.inc?
For example on indexoutofbounds exception?
http://www.msegui.homepage.bluewin.ch/pics/exception.png
http://www.msegui.homepage.bluewin.ch/pics/debugoptions.png
Martin Schreiber wrote:
On Saturday 28 February 2009 11:07:48 Mattias Gaertner wrote:
On Sat, 28 Feb 2009 09:57:05 +0100
And how does MSEGui find lists.inc?
For example on indexoutofbounds exception?
http://www.msegui.homepage.bluewin.ch/pics/exception.png
Hello, FPC developers' list
We have a trouble in lazarus. We need to open units and include files
wich gdb returns to us. The problem is that gdb repors them without full
path.
At moment if we get some file we expand it path using known project and
packages paths (lcl is a package too).
But
On 27 Feb 2009, at 15:17, Paul Ishenin wrote:
We have a trouble in lazarus. We need to open units and include
files wich gdb returns to us. The problem is that gdb repors them
without full path.
It's because there is no path information in the debug information.
What solution fpc team
Zitat von Jonas Maebe jonas.ma...@elis.ugent.be:
On 27 Feb 2009, at 15:17, Paul Ishenin wrote:
We have a trouble in lazarus. We need to open units and include
files wich gdb returns to us. The problem is that gdb repors them
without full path.
It's because there is no path information
In our previous episode, Jonas Maebe said:
In case of DWARF, the path is split in two parts: a base directory,
and then paths to files relative to this base directory. That makes it
easier to specify full paths and still be portable to other file
system layouts, I guess (although I don't
On 27 Feb 2009, at 15:55, Marco van de Voort wrote:
In our previous episode, Jonas Maebe said:
In case of DWARF, the path is split in two parts: a base directory,
and then paths to files relative to this base directory. That makes
it
easier to specify full paths and still be portable to
Feel free to file a feature request
what about patch? :) what units should be studied to make such patch?
Thanks,
Dmitry
P.S. AFAIK, Marc told me, that FPC does not generate DWARF line info
for yet, so it's not possible to use DWARF to find files or anything
else... I don't remember exact, so i
Mattias Gärtner wrote:
Thanks for the advice.
Paul, will you do that?
I've done: http://bugs.freepascal.org/view.php?id=13248
I have no idea whether more info must be placed there? The only thing is
that we need to have this problem solved before lazarus 1.0 release or
we need to invent
On 27 Feb 2009, at 16:08, dmitry boyarintsev wrote:
Feel free to file a feature request
what about patch? :) what units should be studied to make such patch?
compiler/dbgstabs.pas
P.S. AFAIK, Marc told me, that FPC does not generate DWARF line info
for yet, so it's not possible to use
Jonas Maebe wrote:
On 27 Feb 2009, at 16:08, dmitry boyarintsev wrote:
Feel free to file a feature request
what about patch? :) what units should be studied to make such patch?
compiler/dbgstabs.pas
P.S. AFAIK, Marc told me, that FPC does not generate DWARF line info
for yet, so it's not
19 matches
Mail list logo
