Re: [patch 1/2] Re: Crash regression(?) printing Fortran strings in bt [Re: [V2 00/23] Fortran dynamic array support]

[Jan Kratochvil <jan.kratochvil@redhat.com>]

On Thu, 21 Aug 2014 09:27:21 +0200, Keven Boell wrote:
> Since it seems that your environment differs from a clean FC20, it is hard for me to
> reproduce and debug the issues you observe.

I understand this is a problem as I was not able to reproduce it in a clean VM
myself.

But thanks for the information you are still unable to reproduce it, I was not
sure.  I will look more what it cause, I have to debug the problem myself now.


> E.g. if I try to execute your compiled GDB on FC20 32bit, I get errors that some
> shared libraries are missing (e.g. libbabeltrace.so.1).
> So I wonder how we should go on from here?

# repoquery -q --whatprovides libbabeltrace.so.1
libbabeltrace-0:1.2.1-1.fc20.i686
# yum install libbabeltrace.so.1


> > Tested 15f4f87976493f6e144a9bdb5eb7f0109543a393:
> > 
> > runtest gdb.fortran/dynamic-other-frame.exp
> > [...]
> > (gdb) bt^M
> > #0  0x000000000040071d in bar_ ()^M
> > #1  0x00000000004006c7 in foo (string=gdbtypes.c:2009: internal-error: dynamic_prop_get_const_val_ptr: Assertion `prop->kind == PROP_CONST' failed.^M
> > A problem internal to GDB has been detected,^M
> > 
> > Fedora {20,21} {x86_64,i686}: internal-error
> > Fedora {21,21} x86_64 -m32: PASS
> > 
> > But it depends on something suspicious, for a given build the testsuite
> > results are stable but for builds done at different time / under different
> > configurations the results differ.
> 
> Do you know what configuration exactly caused this?

I have built it yesterday with my script "errs12 --noasan" (not providing the
script as it may be misleading) but I was building it with internal-error even
with plain 'CFLAGS=-g ./configure; make' for past mail bugreports.


> I've pushed the dynamic-other-frame test to our Github repository.
> Could you please try to compile and run the tests on a clean FC20 32bit machine?

When I run it on FC20 32bit VM it really does not crash.

It crashes for me in:
	mock -r fedora-20-x86_64 --init
	mock -r fedora-20-x86_64 --shell
	yum install ...
	# even x86_64->i686
but it is all a bit customized so that clean mock may also not reproduce it.


I find it enough that you confirm you still have it unreproducible, I was not
sure.  I will reply more later.


Thanks,
Jan