[GRASS-dev] [bug #5341] (grass) v.db.select: segfault

mneteler wrote (Mon, Nov 27 2006 12:00:12):

I have just tried on my RHEL4 64bit box, works:

For me, on Ubuntu Breezy/32bit AMD K7 and on Ubuntu Dapper/32bit Pentium M it
segfaults.

Guys,

Could other please try and report? Thanks!

Can you please try to debug it? It's fairly easy with 'ddd',
see this for a graphical guide:

I have already put the backtrace there (see above); do you mean something else?

We need to better understand where and how it fails (or
login into your machine).

I could arrange that. Is ssh session OK? I'd only need your IP and I can set
it up for you tommorrow about noon.

Maciek

-------------------------------------------- Managed by Request Tracker

Maciek Sieczka via RT wrote on 11/27/2006 06:53 PM:

mneteler wrote (Mon, Nov 27 2006 12:00:12):

I have just tried on my RHEL4 64bit box, works:
    
For me, on Ubuntu Breezy/32bit AMD K7 and on Ubuntu Dapper/32bit Pentium M it
segfaults.

Guys,

Could other please try and report? Thanks!

Can you please try to debug it? It's fairly easy with 'ddd',
see this for a graphical guide:
    

I have already put the backtrace there (see above); do you mean something else?
  
Yes: use 'ddd'. The gdb backtrace I don't understand.
'ddd', the graphical frontend to gdb, will get you to the offending line.
There you can check variable settings before the program crashes and so
forth.

We need to better understand where and how it fails (or
login into your machine).

I could arrange that. Is ssh session OK? I'd only need your IP and I can set
it up for you tommorrow about noon.

Maybe you could give 'ddd' a try first? It's really not so difficult.

Markus

On Mon, 2006-11-27 at 18:53 +0100, Maciek Sieczka via RT wrote:

mneteler wrote (Mon, Nov 27 2006 12:00:12):

> I have just tried on my RHEL4 64bit box, works:

For me, on Ubuntu Breezy/32bit AMD K7 and on Ubuntu Dapper/32bit Pentium M it
segfaults.

Guys,

Could other please try and report? Thanks!

> Can you please try to debug it? It's fairly easy with 'ddd',
> see this for a graphical guide:

I have already put the backtrace there (see above); do you mean something else?

> We need to better understand where and how it fails (or
> login into your machine).

I could arrange that. Is ssh session OK? I'd only need your IP and I can set
it up for you tommorrow about noon.

I just downloaded the test dataset (from original email) and executed
v.db.select with the parameters specified (it's MAPS_COVER, not
MAP_COVER). Everything completes fine for me and without error.

--
Brad Douglas <rez touchofmadness com> KB8UYR/6
Address: 37.493,-121.924 / WGS84 National Map Corps #TNMC-3785

Yes: use 'ddd'. The gdb backtrace I don't understand.
'ddd', the graphical frontend to gdb, will get you to the offending line.
There you can check variable settings before the program crashes and so
forth.

for ddd/kdbg instructions see doc/debugging.txt in the source code.

Hamish