_CStrxfrm
Re: _CStrxfrm
A debug (malloc?) lib that calls printf?
Mario Charest wrote:
Mario Charest wrote:
I'm profiling an application and I am seeing the fonction _CStrxfrm being
called a lot. It seems the fonction is called by memcpy but _CStrxfrm is an
odd function name to be called by memcpy?
- Mario
Re: _CStrxfrm
"Garry Turcotte" <garry@qnx.com> wrote in message
news:evlolg$8va$1@inn.qnx.com...
news:evlolg$8va$1@inn.qnx.com...
is what you are asking?A debug (malloc?) lib that calls printf?
I'm not sure I'm following. I'm not using the libmalloc_g library if that
Mario Charest wrote:
I'm profiling an application and I am seeing the fonction _CStrxfrm being
called a lot. It seems the fonction is called by memcpy but _CStrxfrm is
an odd function name to be called by memcpy?
- Mario
Re: _CStrxfrm
Just a guess that something was overriding memcpy.
memcpy from libc does not call _CStrxfrm
Mario Charest wrote:
memcpy from libc does not call _CStrxfrm
Mario Charest wrote:
"Garry Turcotte" <garry@qnx.com> wrote in message
news:evlolg$8va$1@inn.qnx.com...
A debug (malloc?) lib that calls printf?
I'm not sure I'm following. I'm not using the libmalloc_g library if that
is what you are asking?
Mario Charest wrote:
I'm profiling an application and I am seeing the fonction _CStrxfrm being
called a lot. It seems the fonction is called by memcpy but _CStrxfrm is
an odd function name to be called by memcpy?
- Mario
Re: _CStrxfrm
Could it be a gcc builtin? Maybe compile with
-fno-builtin.
-seanb
Garry Turcotte <garry@qnx.com> wrote:
-fno-builtin.
-seanb
Garry Turcotte <garry@qnx.com> wrote:
Just a guess that something was overriding memcpy.
memcpy from libc does not call _CStrxfrm
Mario Charest wrote:
"Garry Turcotte" <garry@qnx.com> wrote in message
news:evlolg$8va$1@inn.qnx.com...
A debug (malloc?) lib that calls printf?
I'm not sure I'm following. I'm not using the libmalloc_g library if that
is what you are asking?
Mario Charest wrote:
I'm profiling an application and I am seeing the fonction _CStrxfrm being
called a lot. It seems the fonction is called by memcpy but _CStrxfrm is
an odd function name to be called by memcpy?
- Mario
Re: _CStrxfrm
Are you sure you are using the same version of libc in your debug
environment that is used in the target. I have seen 'apparent'
discrepancies like this when the versions are NOT the same.
Sean Boudreau wrote:
environment that is used in the target. I have seen 'apparent'
discrepancies like this when the versions are NOT the same.
Sean Boudreau wrote:
Could it be a gcc builtin? Maybe compile with
-fno-builtin.
-seanb
Garry Turcotte <garry@qnx.com> wrote:
Just a guess that something was overriding memcpy.
memcpy from libc does not call _CStrxfrm
Mario Charest wrote:
"Garry Turcotte" <garry@qnx.com> wrote in message
news:evlolg$8va$1@inn.qnx.com...
A debug (malloc?) lib that calls printf?
I'm not sure I'm following. I'm not using the libmalloc_g library if that
is what you are asking?
Mario Charest wrote:
I'm profiling an application and I am seeing the fonction _CStrxfrm being
called a lot. It seems the fonction is called by memcpy but _CStrxfrm is
an odd function name to be called by memcpy?
- Mario
Re: _CStrxfrm
"Warren Deitch" <warren.deitch@transtoll.com> wrote in message
news:evpoet$aee$1@inn.qnx.com...
from a windows host and yes they don't have the same version NTO is
SP3+6.3.2 and Windows is SP3 only.
news:evpoet$aee$1@inn.qnx.com...
Hum, the code is build and run on the same QNX6 machine. But I'm debuggingAre you sure you are using the same version of libc in your debug
environment that is used in the target. I have seen 'apparent'
discrepancies like this when the versions are NOT the same.
from a windows host and yes they don't have the same version NTO is
SP3+6.3.2 and Windows is SP3 only.
Sean Boudreau wrote:
Could it be a gcc builtin? Maybe compile with
-fno-builtin.
-seanb
Garry Turcotte <garry@qnx.com> wrote:
Just a guess that something was overriding memcpy.
memcpy from libc does not call _CStrxfrm
Mario Charest wrote:
"Garry Turcotte" <garry@qnx.com> wrote in message
news:evlolg$8va$1@inn.qnx.com...
A debug (malloc?) lib that calls printf?
I'm not sure I'm following. I'm not using the libmalloc_g library if
that is what you are asking?
Mario Charest wrote:
I'm profiling an application and I am seeing the fonction _CStrxfrm
being called a lot. It seems the fonction is called by memcpy but
_CStrxfrm is an odd function name to be called by memcpy?
- Mario
Re: _CStrxfrm
"Mario Charest" <root@127.0.0.1> wrote in message
news:evvs56$ace$1@inn.qnx.com...
everything was fine.
news:evvs56$ace$1@inn.qnx.com...
Good catch, thanks. That was it. Once I updated the windows host to 6.3.2"Warren Deitch" <warren.deitch@transtoll.com> wrote in message
news:evpoet$aee$1@inn.qnx.com...
Are you sure you are using the same version of libc in your debug
environment that is used in the target. I have seen 'apparent'
discrepancies like this when the versions are NOT the same.
Hum, the code is build and run on the same QNX6 machine. But I'm
debugging from a windows host and yes they don't have the same version NTO
is SP3+6.3.2 and Windows is SP3 only.
everything was fine.
Sean Boudreau wrote:
Could it be a gcc builtin? Maybe compile with
-fno-builtin.
-seanb
Garry Turcotte <garry@qnx.com> wrote:
Just a guess that something was overriding memcpy.
memcpy from libc does not call _CStrxfrm
Mario Charest wrote:
"Garry Turcotte" <garry@qnx.com> wrote in message
news:evlolg$8va$1@inn.qnx.com...
A debug (malloc?) lib that calls printf?
I'm not sure I'm following. I'm not using the libmalloc_g library if
that is what you are asking?
Mario Charest wrote:
I'm profiling an application and I am seeing the fonction _CStrxfrm
being called a lot. It seems the fonction is called by memcpy but
_CStrxfrm is an odd function name to be called by memcpy?
- Mario