On Monday 03 March 2008 12:01, Tom Hughes wrote:
> I'm getting thousands of messages along these lines when I turn
> on reading of variable info:
>
> --29598-- warning: addVar: in range 0xFA08 .. 0xFA12 outside segment
> 0x36DD005210 .. 0x36DD00FC07 (ignore)
(Background, for the benefit of the ar
On Monday 03 March 2008, Julian Seward wrote:
> I intend to merge the DATASYMS branch to trunk shortly.
Hi Julian,
some time ago there was the wish for a call tree trace similar to
strace/ltrace via valgrind. Can your machinary help to add parameter
name/type information the such a call tree trac
Fixed (r7551).
J
On Monday 03 March 2008 20:33, Bart Van Assche wrote:
> On Mon, Mar 3, 2008 at 12:51 AM, Julian Seward <[EMAIL PROTECTED]> wrote:
> > Because the changes are mostly self contained, I don't expect
> > this merge to cause any serious problems. Please complain if
> > they do.
>
On Mon, Mar 3, 2008 at 12:51 AM, Julian Seward <[EMAIL PROTECTED]> wrote:
> Because the changes are mostly self contained, I don't expect
> this merge to cause any serious problems. Please complain if
> they do.
The following command triggers a segmentation fault on my system:
./vg-in-place -
> --29598-- warning: addVar: in range 0xFA08 .. 0xFA12 outside segment
> 0x36DD005210 .. 0x36DD00FC07 (ignore)
And just when I thought I had it all working :-)
Looks like a failure to add on the text bias at some point. Can you
send me the relevant .so to look at?
J
--
In message <[EMAIL PROTECTED]>
Julian Seward <[EMAIL PROTECTED]> wrote:
> Memcheck is able to make use of Dwarf3 info if it has been read,
> but does not read it by default. To allow users to force this
> information to be read, a flag --read-var-info=yes has been
> added. This is a core
On Mon, 3 Mar 2008, Julian Seward wrote:
> On Monday 03 March 2008 04:17, Nicholas Nethercote wrote:
>> On Mon, 3 Mar 2008, Julian Seward wrote:
>>> Location 0x7feffba09 is 1 byte inside a[3].xyzzy[21].c2[2],
>>> declared at varinfo4.c:45, in frame #1 of thread 1
>>
>> What's the frame number?
>
On Monday 03 March 2008 04:17, Nicholas Nethercote wrote:
> On Mon, 3 Mar 2008, Julian Seward wrote:
> > Location 0x7feffba09 is 1 byte inside a[3].xyzzy[21].c2[2],
> > declared at varinfo4.c:45, in frame #1 of thread 1
>
> What's the frame number?
It tries to locate an address in all call frame
On Mon, 3 Mar 2008, Julian Seward wrote:
> Location 0x7feffba09 is 1 byte inside a[3].xyzzy[21].c2[2],
> declared at varinfo4.c:45, in frame #1 of thread 1
What's the frame number?
The rest sounds good to me.
N
-
This SF
