Thread View: gnu.utils.bug
2 messages
2 total messages
Started by Shiva Ramabadran
Thu, 27 Aug 1992 15:39
GNU regex routines.(for xxgdb) on AIX
Author: Shiva Ramabadran
Date: Thu, 27 Aug 1992 15:39
Date: Thu, 27 Aug 1992 15:39
32 lines
1545 bytes
1545 bytes
Hi, I'm trying to use the GNU regex routines that are available as part of _many_ GNU products. (emacs-18.58, gdb-4.5, xxgdb-1.06, to name a few.) I'm running into problems using them on an Rs/6000 running AIX 3.1 (or 3.2 for that matter.) Specifically, I'm trying to compile xxgdb on an rs/6000 and running into problems with Regexp parsing using these routines. It SEGV's attempting recognize the most simple of regexp's like '[ ]*'. Has anyone been able to use these on an Rs/6000 ? I'd suspect that it is a memory leak which fails to get past AIX's stringent memory management scheme. The same code works on a Sun and other platforms. Has anyone got xxgdb working on an Rs/6000 ? Is there a newer version of this code that I can ftp from anywhere ? The regex.[ch] that is part of the above GNU products does not seem to work on Rs/6000's. Any help will be appreciated. Thanks, -Shiva -=- ITS Systems Programmer.
Re: GNU regex routines.(for xxgdb) on AIX
Author: Joachim Schrod
Date: Fri, 28 Aug 1992 14:52
Date: Fri, 28 Aug 1992 14:52
28 lines
1646 bytes
1646 bytes
In article <y-qyrwk@rpi.edu>, ramabs2@rpi.edu (Shiva Ramabadran) writes: > > I'm running into problems using them on an Rs/6000 running > AIX 3.1 (or 3.2 for that matter.) Specifically, I'm trying to > compile xxgdb on an rs/6000 and running into problems with Regexp > parsing using these routines. > > It SEGV's attempting recognize the most simple of regexp's > like '[ ]*'. Have you applied the patch Torsten Ohl posted a few months ago? Basically, the regexp package do not work when alloca() is used to get the space for the nodes. Then storage is accessed (with a read operation) which is never allocated; that can cause a SEGV like in your case. There is a #define at the very top to discard the usage of alloca(), use this. Oh yes, a good tool for analyzing such errors is the debugging malloc library (posted in c.s.r and available from all good archives). -- Joachim =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: schrod@iti.informatik.th-darmstadt.de Computer Science Department Technical University of Darmstadt, Germany
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads