octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

is_defined() again [Was: Follow up on profiler development]


From: Daniel Kraft
Subject: is_defined() again [Was: Follow up on profiler development]
Date: Wed, 10 Aug 2011 11:19:45 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20110624 Thunderbird/5.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi again,

I just observed an "interesting" segfault while working on hierarchical
profiling (but it happens as well with the version without my work in
progress):

Running "demo profshow" three times in a row makes Octave segfault --
but GDB shows that the segfault happens not inside some profiler data
collection routine (which I first thought, since I reworked them for
hierarchical profiling) but rather with is_defined().  This routine
becomes more and more mystical to me over time! :D

Any ideas?  But until the problem occurs in a more "direct" situation,
I'll defer this to later.  (Of course, maybe it is still a problem with
my profiler code which corrupts some memory but leads only later to a
segfault ... or something.  Maybe I'll try to run Octave through
valgrind to find that out -- any experience with that?  Does it work?)

Yours,
Daniel

PS: Regarding the hierarchical profiler, I now have the data collection
routines in a state that reproduces the flat profile correctly; but
internally reworked so that the data collection takes place in form of a
hierarchical call-tree rather than the flat table directly.  Next will
be interfacing the hierarchical data to the outside world.

- -- 
OpenPGP: 3BA2 3DDB 7758 F010 BDAB 0DCF 527E 79BA A3B5 3998
or use https://safesend.domob.eu/
- --
Done:  Arc-Bar-Cav-Kni-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Mon-Pri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOQk0wAAoJEFJ+ebqjtTmYMlQP/Rd3tYhs7yiBYMizDQEkMiIs
+VBQUG+woUB7UbHuZNAVgrablAKtOvOFZ2PKS6NRQ6yLCCYKSOC93GWjbNuu4U9m
BCVomXyFIB7DFZ3Oa5IYAmAxTTHtxYE7hWLF9DDCSyBXVvSozb05tFpvqrUULQ+U
+P2yhu69c4aWQ/ThAP9tAa7xYa2g/mKjmZgd63bywC8H4uWi1B/FeJeIdko0L05k
AHbPqkfp9rGoBNI37gwxaN7jGNgH2SPA52TQ3ylWhMrzXDYLjhwgXDzaPfksJagW
skj0aEbfrp3xURCDmZnqLxrk21BBY+9y3nbapN/+ebIYD0JE6o+dO0J2P4UieTMg
ieyp7pGcEpzAezgKi14MZjBll9O4gupKmCC0nkciMVh+ObDKj5ZJNUTLIDXY7+63
w6lx24hzi9UtqVq1vO5KqkA0gDXFYCLmq2aQvpaE9l/vqmy3+K/HyAXgAekyMWWX
e1CjFE8nAG9v4xThciDD2u2KP94iSy+yERr4sWfwJKYww/Ji1Af4KLUzMpbZ39Gg
ZVrXKf37sJUlW8MCjBgR3bpuGUwNmlBVRXJ5tD/+f4NFOXX2D0ePu6g6vzCyZnMc
5binpxHanNN+v/W4KlcbBOuv0aSeJWobqhwOdurKLpO7GcLvyA7DOZAhRSPboYQz
yn634QZgB5t1VTgkadYz
=kKVD
-----END PGP SIGNATURE-----

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]