Hi, I find that doing an operation such as : (gdb) p Attribute::dump(&temp_attr) Segmentation fault fails on gdb-4.18 (the debugger cores). The details are as follows: HW: HP PA-RISC K370 OS: HP-UX 10.20, March 2000 patchset gdb-4.18 was compiled with gcc-2.95.2 my test code is compiled with HP's CC /usr/local/bin/gdb-4.18 --version GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "hppa1.1-hp-hpux10.20". I think this may be a regression, since HP's WDB is based on gdb-4.17, and doesn't seem to have a problem with this: (gdb) p Attribute::dump(&temp_attr) "ip_address" : "172.16.2.248" /opt/langtools/bin/gdb --version HP gdb D49 Beta1.0 Copyright 1986 - 1999 Free Software Foundation, Inc. Hewlett-Packard Wildebeest D49 Beta1.0 (based on GDB 4.17-hpwdb-980821) Wildebeest is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for Wildebeest. Type "show warranty" for details. Wildebeest was built for PA-RISC 1.1 or 2.0 (narrow), HP-UX 10.20. I doubt that HP has done something special to make this work; if they have, then they should have submitted a patch. If they haven't, surely they will be violating the GPL by distributing a binary based on modified source? Thanks for any help on this, -- Andrew Gaylard andrew.gaylard @ bsw . co . za
