From knepley at gmail.com Fri May 15 16:12:51 2026 From: knepley at gmail.com (Matthew Knepley) Date: Fri, 15 May 2026 17:12:51 -0400 Subject: [petsc-dev] Debugging a Doc Error Message-ID: Does anyone know how to find out which file is causing this? https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/jobs/14396278578__;!!G_uCfscf7eWS!cti40YuOePJaP0duRMM0I0iSShI4Ss4Tc97ZeH8JefuyPQ6aNa6MwNfdQfBakHHkIZD4ZOdj2Br2b3qD8X8u$ I cannot for the life of me decode this error message. Thanks, Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener https://urldefense.us/v3/__https://www.cse.buffalo.edu/*knepley/__;fg!!G_uCfscf7eWS!cti40YuOePJaP0duRMM0I0iSShI4Ss4Tc97ZeH8JefuyPQ6aNa6MwNfdQfBakHHkIZD4ZOdj2Br2b6Q399mE$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsmith at petsc.dev Fri May 15 17:28:40 2026 From: bsmith at petsc.dev (Barry Smith) Date: Fri, 15 May 2026 18:28:40 -0400 Subject: [petsc-dev] Debugging a Doc Error In-Reply-To: References: Message-ID: <7D0BA866-347E-41DF-B962-B1BA9725D817@petsc.dev> You were sloppy when you did something illegal in PETSc :-) /*PetscCheck(depth == dim, Leaving commented out code in an MR and not ensuring a space after /* for all comments > On May 15, 2026, at 5:12?PM, Matthew Knepley wrote: > > Does anyone know how to find out which file is causing this? > > https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/jobs/14396278578__;!!G_uCfscf7eWS!YA4VCJddxteTxl6TVNehLQG9YhtnzcQTA4L3M97J_gzOac-xjhvw-DDLf9JnICTdFetMhrK3s-TZnFdaLYBEAg$ > > I cannot for the life of me decode this error message. > > Thanks, > > Matt > > -- > What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. > -- Norbert Wiener > > https://urldefense.us/v3/__https://www.cse.buffalo.edu/*knepley/__;fg!!G_uCfscf7eWS!YA4VCJddxteTxl6TVNehLQG9YhtnzcQTA4L3M97J_gzOac-xjhvw-DDLf9JnICTdFetMhrK3s-TZnFcDxF7jPg$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsmith at petsc.dev Fri May 15 17:34:11 2026 From: bsmith at petsc.dev (Barry Smith) Date: Fri, 15 May 2026 18:34:11 -0400 Subject: [petsc-dev] Debugging a Doc Error In-Reply-To: <7D0BA866-347E-41DF-B962-B1BA9725D817@petsc.dev> References: <7D0BA866-347E-41DF-B962-B1BA9725D817@petsc.dev> Message-ID: <892E05EC-67BB-4DFE-AFC9-E1A966E89896@petsc.dev> I found it by looking for corrupt entries in manualpages.cit > On May 15, 2026, at 6:28?PM, Barry Smith wrote: > > You were sloppy when you did something illegal in PETSc :-) > > /*PetscCheck(depth == dim, > > Leaving commented out code in an MR and not ensuring a space after /* for all comments > > > > >> On May 15, 2026, at 5:12?PM, Matthew Knepley wrote: >> >> Does anyone know how to find out which file is causing this? >> >> https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/jobs/14396278578__;!!G_uCfscf7eWS!YyLPlBL4WTL4n8PtOkPAQNkEOIpfrLE0JLDxer0g9XGIyMz7VZKUqhfwbbwxQMSZgobPzZYUFKThLF00UCmvqw$ >> >> I cannot for the life of me decode this error message. >> >> Thanks, >> >> Matt >> >> -- >> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. >> -- Norbert Wiener >> >> https://urldefense.us/v3/__https://www.cse.buffalo.edu/*knepley/__;fg!!G_uCfscf7eWS!YyLPlBL4WTL4n8PtOkPAQNkEOIpfrLE0JLDxer0g9XGIyMz7VZKUqhfwbbwxQMSZgobPzZYUFKThLF0ui_aMHw$ > -------------- next part -------------- An HTML attachment was scrubbed... URL: