Re: random debugging, What should I prepare for a PL PhD program

Thomas Koenig <tkoenig@netcologne.de>
Sun, 23 Oct 2022 09:28:43 -0000 (UTC)

          From comp.compilers

Related articles
[3 earlier articles]
Re: What should I prepare for a PL PhD program spibou@gmail.com (Spiros Bousbouras) (2022-10-21)
Re: What should I prepare for a PL PhD program tkoenig@netcologne.de (Thomas Koenig) (2022-10-21)
Re: random debugging, What should I prepare for a PL PhD program gah4@u.washington.edu (gah4) (2022-10-21)
Re: random debugging, What should I prepare for a PL PhD program tkoenig@netcologne.de (Thomas Koenig) (2022-10-22)
Re: random debugging, What should I prepare for a PL PhD program DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2022-10-23)
Re: random debugging, What should I prepare for a PL PhD program gah4@u.washington.edu (gah4) (2022-10-23)
Re: random debugging, What should I prepare for a PL PhD program tkoenig@netcologne.de (Thomas Koenig) (2022-10-23)
| List of all articles for this month |

From: Thomas Koenig <tkoenig@netcologne.de>
Newsgroups: comp.compilers
Date: Sun, 23 Oct 2022 09:28:43 -0000 (UTC)
Organization: news.netcologne.de
References: 22-10-029 22-10-031 22-10-035 22-10-036 22-10-039 22-10-040 22-10-042 22-10-049
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="84775"; mail-complaints-to="abuse@iecc.com"
Keywords: testing
Posted-Date: 23 Oct 2022 12:31:15 EDT

Hans-Peter Diettrich <DrDiettrich1@netscape.net> schrieb:
> On 10/22/22 10:49 AM, Thomas Koenig wrote:
>
>> An automated code generator which generates valid programs according
>> to the syntax and semantics rules of a langauge and then systematically
>> violates the rules (especially those prescribed outside the formal
>> grammar) one by one might be possible. Alternatively, it might
>> also be feasible to parse an existing code base and systematically
>> insert violations there.
>
> Isn't it good practice to maintain a test suite at least for compilers,
> that contains both selected valid and invalid code snippets?


Very much so.


For example, gcc requires two things for a patch: There needs to
be a test case to make sure that the bug is fixed, or the added
feature keeps on working, and the submitter needs to run the
testsuite to make sure that all other tests continue to work.


This is a good approach, but it has the same basic limitations of
all testsuites: They are never complete, and they also contain
compiler-specific code and also some errors.


> For error reports on obviously weird input I'd prepare an equally weird
> answer ;-)


If you have seen enough strange bug reports, it might be equally
challenging to come up with something new as to actually fix the
bug :-)


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.